Track Factory Droid CLI 0.164.1 upstream release

[a5c-ai]

Upstream version check

• Agent: Factory Droid CLI
• Package: @factory/cli
• Previously recorded in graph: 0.164.0
• Latest checked version: 0.164.1
• Package metadata: https://www.npmjs.com/package/@factory/cli/v/0.164.1

Research notes

I checked npm metadata for @factory/cli. The latest version is 0.164.1, published July 6, 2026. The package metadata points to git+https://github.com/Factory-AI/factory.git with directory apps/cli, and the README still documents npm install -g @factory/cli, running droid from a project directory, and the ! bash-mode toggle. I did not find public per-version release notes for 0.164.1 in the official package metadata or GitHub release surfaces checked during this run.

Changes found

• New npm package version only.
• No confirmed new CLI flags.
• No confirmed transport/API changes.
• No confirmed model/tool capability changes.
• No install method or package-name change; install remains npm install -g @factory/cli.

Likely affected system surfaces

• Atlas AgentVersion graph should record the new package version and package-metadata evidence.
• Adapter launchBehavior does not need a flag update based on available public metadata.
• Install instructions remain unchanged.

Migration notes

No migration steps were published.

Assimilation checklist

• Update AgentVersion graph for Factory Droid CLI 0.164.1.
• Keep install command as npm install -g @factory/cli.
• Verify droid launchBehavior remains unchanged because no new flags were published.
• Record package-metadata evidence because no release notes were found.

[a5c-ai]

Triage Summary

• One-line: Track the upstream @factory/cli package moving from the graph-recorded Factory Droid CLI 0.164.0 to 0.164.1.

Critical Evaluation

• Reporter's analysis is accurate: npm metadata confirms @factory/cli latest is 0.164.1, published on 2026-07-06, while the local Atlas graph still records Factory Droid CLI 0.164.0.
• This is not a runtime adapter bug. It is a narrow Atlas graph/catalog freshness update.
• Do not infer CLI behavior, transport, API, model, MCP, install, or migration changes from package metadata alone.

Root Cause Analysis

• Affected files:
  • packages/atlas/graph/agent-stack/agent-versions/upstream-current-2026-07-03.yaml
  • packages/atlas/graph/catalog-meta/evidence-sources/ for the matching package-metadata evidence shard
• Current code evidence:
  • The latest Droid AgentVersion entry is agentVersion:droid:0-164-0.
  • It records currentVersion: "0.164.0" and releaseNotesUrl: "https://www.npmjs.com/package/@factory/cli/v/0.164.0".
  • rg -n "0\\.164\\.1" found no existing graph/evidence entry.
• Upstream evidence:
  • npm view @factory/cli version time repository dist-tags --json reports dist-tags.latest: "0.164.1".
  • Package repository metadata remains git+https://github.com/Factory-AI/factory.git, directory apps/cli.

Affected Components

• Packages: atlas, agent-catalog
• Effort: effort:small

Recommended Approach

• Add or update the Droid AgentVersion record for @factory/cli 0.164.1.
• Add package-metadata evidence for the npm package version.
• Keep install command as npm install -g @factory/cli.
• Keep adapter launch behavior unchanged unless independent release evidence proves a behavior change.
• Run npm run verify:metadata after editing graph/evidence records.

Reproduction

npm view @factory/cli version time repository dist-tags --json
rg -n "0\\.164\\.1|0\\.164\\.0" packages/atlas/graph/agent-stack/agent-versions packages/atlas/graph/catalog-meta/evidence-sources

Related Issues/PRs

• Related prior version issue: Track Factory Droid CLI 0.164.0 upstream release #1131 tracked Factory Droid CLI 0.164.0.
• No separate duplicate issue was found for 0.164.1.
• No closed PR or commit was found that already assimilates 0.164.1.

Priority

• priority:low
• Routine upstream package-version assimilation for Atlas graph metadata. It improves catalog freshness but does not block production workflows.

Risk Analysis

• Risk Level: risk:low
• Catalog accuracy risk: Do not overstate behavior changes from package metadata alone.
  • Mitigation: Limit changes to AgentVersion/evidence metadata unless official release notes confirm behavior changes.
• Graph consistency risk: Duplicate or mismatched graph/evidence IDs can break metadata checks.
  • Mitigation: Follow existing upstream-current naming conventions and run npm run verify:metadata.
• Adapter regression risk: Changing launch behavior without evidence could cause avoidable breakage.
  • Mitigation: Do not edit adapter behavior for this issue.

[a5c-ai]

Triage Summary

• One-line: Track Factory Droid CLI 0.164.1 in Atlas graph/catalog metadata with package-metadata evidence.

Critical Evaluation

• Reporter's analysis is accurate.
• This is not a runtime Droid adapter bug. It is an AgentVersion/evidence assimilation task for the Atlas graph.

Root Cause Analysis

• Affected files:
  • packages/atlas/graph/agent-stack/agent-versions/upstream-current-2026-07-03.yaml
  • packages/atlas/graph/agent-stack/versions/droid-current.yaml
  • packages/atlas/src/catalog/catalog.test.ts
  • package.json
• The latest dated Droid AgentVersion found in the graph is agentVersion:droid:0-164-0, with currentVersion: "0.164.0" and npm metadata URL /v/0.164.0.
• packages/atlas/graph/agent-stack/versions/droid-current.yaml is older and still records currentVersion: "0.136.1". Check whether this file is still consumed before deciding whether to update it or leave it as legacy data.
• No commit or closed PR found during triage appears to assimilate 0.164.1.

Affected Components

• Packages: atlas, agent-catalog
• Effort: effort:small

Recommended Approach

Treat this as an Atlas graph AgentVersion/evidence update, not an adapter behavior change.

• Add a 0.164.1 Droid AgentVersion entry with source-backed npm metadata evidence for @factory/cli 0.164.1.
• Preserve install and launch behavior unless fresh upstream evidence proves a CLI flag, transport, model, install, or migration change.
• Before editing, identify which Droid current-version surfaces are live catalog inputs. Update all live surfaces consistently, or explicitly leave legacy surfaces unchanged.
• Run npm run verify:metadata, npm run build:atlas, and the Atlas catalog contract tests that cover graph-backed AgentVersion loading.

Reproduction

rg -n "0\\.164\\.1|0\\.164\\.0|@factory/cli" packages/atlas/graph

Expected: a Factory Droid 0.164.1 AgentVersion/evidence record.

Actual: only 0.164.0 and older Droid records are found.

Related Issues/PRs

• Track Factory Droid CLI 0.164.0 upstream release #1131 tracks the previous Factory Droid CLI 0.164.0 release and is closed.
• Earlier related version-tracking issues include Track Factory Droid CLI 0.162.1 #1112, Track Factory Droid CLI 0.161.0 #1079, Track Factory Droid CLI 0.161.0 #1055, Track Factory Droid CLI 0.156.2 #1019, Track Factory Droid CLI 0.156.2 #1033, Track Factory Droid CLI 0.150.1 #982, Track Factory Droid CLI 0.150.1 #968, Track Factory Droid CLI 0.141.0 #891, Track Factory Droid 0.137.1 upstream release #812, Track upstream droid-0.136.1 release #543, Track Droid CLI 0.135.0 upstream release #505, Track Droid 0.134.0 upstream release #445, Assimilate Droid 0.132.1 #324, and Track Droid 0.131.0 #303.
• Recent related graph commit found: 9d8fbf02f chore(graph): track upstream agent versions, which added the 0.164.0 Droid block.

Priority

low

This is a routine upstream package-version metadata update. It does not appear to block production workflows, cause data loss, or indicate a runtime adapter regression.

Risk Analysis

• Risk Level: risk:low
• Missing or weak evidence provenance for the 0.164.1 record
  • Mitigation: Add a source-backed npm metadata evidence reference for @factory/cli v0.164.1 and run metadata/catalog validation.
• Inconsistent current-version surfaces across dated AgentVersion records and droid-current.yaml
  • Mitigation: Check the Atlas catalog ingestion path before editing and update all live graph inputs consistently.
• False behavioral claims from version-only metadata
  • Mitigation: Only record confirmed package/version/install facts unless upstream release notes or package metadata confirms CLI, transport, model, or migration changes.