Repository navigation
Capture agents in their own UIs through their hooks (ADR-0013); park ACP - #2
Merged
Merged
Conversation
The product changes direction: agents keep their native UIs and Atlas plugs into their lifecycle hooks, the way the Entire CLI does (docs/research/entire-cli.md), with the Atlas store, cloud sync and shared memory on top. - internal/hooks: the framework. One event set and dispatcher; per-agent Parse, hook config install (raw-map merge, stale-entry pruning, 0600 atomic writes), transcript readers; per-session state under .atlas/hooks/; TurnStart snapshots git status and the transcript offset, TurnEnd reads the transcript from the offset and diffs git status; delivery direct under the writer lock, to a running atlas serve over its socket, or into a spool the next writer drains; a git post-commit hook that links sessions to commits; mcpconfig writers that put the atlas_memory stdio entry into each agent's MCP config. - Agents: Claude Code, Codex, Cursor, GitHub Copilot CLI, OpenCode, Factory Droid, Antigravity, Pi, each verified live on this machine (Droid up to its sign-in). - record.RecordTurn writes a whole captured turn; the listener gains /hook, /mcp over the owner-only socket and Link on /sync; atlas mcp-bridge serves memory with or without a listener and answers a request sent before initialize with method-not-found (Antigravity). - Commands: atlas agents add|remove|list|sessions, hidden atlas hooks, status lines for hooks. The ACP path (atlas run, the chat screen, the registry installs, the ADR-0012 session/load importer) moves under the hidden atlas acp group. - Also lands the ADR-0012 ACP import loop written before the change of direction (internal/run/import.go, atlas acp import). - Docs: ADR-0012, ADR-0013, the Entire research, README, RELEASE checklists, progress with the per-agent live results.
2 tasks done
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
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.
What
Agents keep their native UIs; Atlas plugs into their lifecycle hooks (the Entire CLI's model, researched in
docs/research/entire-cli.md) and records each turn into the Atlas store, with cloud sync and shared memory on top. ADR-0013 records the decision; the ACP path is parked under the hiddenatlas acpgroup.atlas agents add <agent>writes the hook into the agent's config and theatlas_memoryMCP entry into its MCP config, plus a gitpost-commithook.atlas hooks <agent> <verb>: TurnStart snapshots git status and the transcript offset; TurnEnd reads the transcript from the offset, diffs git status, and delivers the turn (directly, to a runningatlas serve, or into a spool). Hooks never fail the agent.atlas mcp-bridge --project … --agent …serves memory with or without a listener.Verified live (this Mac)
Claude Code (
-pand the TUI), Codex, Copilot, OpenCode, Pi, Cursor and Antigravity capture end to end: prompt, replies, tool calls, file touches, usage, memory; commits are linked by the post-commit hook. Droid's hooks fire; the agent needs a Factory sign-in. Per-agent details and the one-time trust steps are indocs/progress.mdand the README.Not yet verified
The desktop parity checklist (
docs/acceptance), and Droid past sign-in.