docs: refresh README + AGENTS.md for 0.2.0 / 0.2.1 - #14
Merged
Conversation
The docs lagged behind two releases. Most of what was wrong: * AGENTS.md still claimed action segments were Anthropic-only and Codex was on the v0.3 list — both have shipped in v0.2.0 (`computeActionSegmentsResponses` in aggregate.ts). * Both files still printed the old `projectId = sha256(cwd)` formula. Since v0.2.0 it's `sha256(cwd \0 agent).slice(0,16)`; mixed-agent legacy files are split per agent on first boot (`maybeReKeyByAgent`). * Privacy section in the README claimed the only outbound traffic was `api.anthropic.com`. With Codex CLI we also forward to `api.openai.com` (sk- keys) or `chatgpt.com/backend-api/codex` (eyJ OAuth) per request. * "No tests yet" in AGENTS.md — we have `pnpm smoke` now (build + scripts/smoke-codex.mjs + scripts/smoke-launcher.mjs). * Codex cwd-extraction recipe still showed the bare `<cwd>…</cwd>` regex, but that anchors on AGENTS.md doc examples and produces garbage cwds. The real rule requires the `<cwd>` to sit inside `<environment_context>` and scans input[] backwards. * Roadmap, file-tree, supported-agents table, and launcher section updated to reflect `agentmind-cli` defaulting to Claude (v0.2.1) and `--no-agent` for dashboard-only mode. Also fixed three stale "0.2.2" version references in source-code comments (storage.ts, smoke-codex.mjs) — those should be 0.2.0. No production-code changes. `pnpm typecheck` is clean.
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The user-facing docs lagged behind the v0.2.0 and v0.2.1 releases. This
pass aligns every stale claim with the current code and bumps a few
out-of-date roadmap items into the done column.
What was wrong
Codex pairing was on the v0.3 list — both shipped in v0.2.0 via
`computeActionSegmentsResponses` (`src/server/aggregate.ts`).
it's `sha256(cwd \0 agent).slice(0,16)`; mixed-agent legacy
files are split per agent on first boot (`maybeReKeyByAgent` in
`storage.ts`).
`api.anthropic.com`. With Codex CLI we now also forward per-
request to `api.openai.com` (Bearer `sk-…`) or
`chatgpt.com/backend-api/codex` (Bearer `eyJ…` OAuth).
capture, Anthropic regression, `(cwd, agent)` scoping, the
legacy split-on-boot, and launcher argv/env injection.
`…` regex — that anchors on AGENTS.md doc examples
and produces garbage cwds. The real rule requires `` inside
`<environment_context>` and scans `input[]` backwards.
section updated to reflect `agentmind-cli` defaulting to Claude
(v0.2.1) and `--no-agent` for dashboard-only mode.
Also fixed
Three stale `0.2.2` version references in source-code comments
(`storage.ts`, `scripts/smoke-codex.mjs`) — those should be
`0.2.0` since that's when the migration actually shipped.
Scope
comments.