f5570b4e5a
- Rename project config dir from .pi/ to .feynman/ (Pi supports this via piConfig.configDir) - Rename citation agent to verifier across all prompts, agents, skills, and docs - Add website with homepage and 24 doc pages (Astro + Tailwind) - Add skills for all workflows (deep-research, lit, review, audit, replicate, compare, draft, autoresearch, watch, jobs, session-log, agentcomputer) - Add Pi-native prompt frontmatter (args, section, topLevelCli) and read at runtime - Remove sync-docs generation layer — docs are standalone - Remove metadata/prompts.mjs and metadata/packages.mjs — not needed at runtime - Rewrite README and homepage copy - Add environment selection to /replicate before executing - Add prompts/delegate.md and AGENTS.md Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
24 lines
853 B
Markdown
24 lines
853 B
Markdown
# ACP Flow
|
|
|
|
The `computer acp serve` bridge makes a remote machine agent look like a local ACP server over stdio.
|
|
|
|
## Basic shape
|
|
|
|
1. The local client starts `computer acp serve <machine> --agent <agent> --name <session>`.
|
|
2. The bridge handles ACP initialization on stdin/stdout.
|
|
3. The bridge maps ACP session operations onto Agent Computer session APIs.
|
|
4. Remote session updates are streamed back as ACP `session/update` notifications.
|
|
|
|
## Good commands
|
|
|
|
```bash
|
|
computer acp serve my-box --agent claude --name research
|
|
computer acp serve gpu-worker --agent claude --name experiment
|
|
```
|
|
|
|
## Recommended client behavior
|
|
|
|
- Reuse a stable session name when reconnecting.
|
|
- Treat the bridge as the single local command for remote-agent interaction.
|
|
- Use the normal `computer agent ...` commands outside ACP when you need manual inspection or cleanup.
|