Repository navigation
chord 0.2.0
Agents run in the project folder
chord claude and chord codex now start the tool in the project folder, the directory you run it in yourself, so that stays its project: one /resume list, one CLAUDE.md, one trust answer. Each agent still works in its own worktree under chord/agents/<name>/. Writes to the main checkout or another agent's worktree are refused with the path of the agent's own copy, and a shell command that ran in the main checkout gets a warning.
The hooks record each agent's conversation id, so chord resume <agent> reopens exactly that conversation for Claude and Codex alike. Agents started with earlier versions have no recorded conversation; start them again with chord <tool> --name <agent>. chord no longer writes trust entries to ~/.claude.json.
Readable commands
chord lsfits the terminal width (CJK counts as two cells), showsbusy,idleoroff 3d, counts only real messages as unread and lists each agent's claims under its row.chord messagesprints one line per send, naming up to three recipients, and drops the sentence meant for agents.chord cleansays what is held (unmerged commits, uncommitted changes) and names the agents a--forcewould hit;-fworks.chord --helpdescribes every command;chord --versionexists; unknown commands and arguments are reported instead of ignored.- Timestamps from another day read
Oct 17 23:39; a quitting agent is told how to come back. - A wrapper killed with its pid reused is no longer shown online for ever:
ls,cleanandstopwatch stale heartbeats for a moment first.
Also
- A Chinese README (
README.zh-CN.md). - The database upgrades itself to schema version 3 on first open; the migration runs under a write lock.
Full changes: v0.1.3...v0.2.0