- 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>
3.4 KiB
3.4 KiB
name, description, allowed-tools
| name | description | allowed-tools |
|---|---|---|
| agentcomputer | Delegate research tasks to remote Agent Computer machines for cloud execution. Manages machine discovery, remote agent sessions, task delegation, progress monitoring, result retrieval, and ACP bridging via the aicomputer CLI. | Bash(npm:*), Bash(npx aicomputer@latest:*), Bash(aicomputer:*), Bash(computer:*) |
Agent Computer
Use Agent Computer to run Feynman research workflows on remote cloud machines when local compute is insufficient or when tasks should run unattended.
When to use
- A research task needs GPU, large memory, or long-running compute
/autoresearchor/deepresearchshould run unattended in the cloud- The user explicitly asks to delegate work to a remote machine
- An experiment loop would take hours and should not block the local session
Prerequisites
The aicomputer CLI must be installed and authenticated:
if command -v computer >/dev/null 2>&1; then
COMPUTER=computer
elif command -v aicomputer >/dev/null 2>&1; then
COMPUTER=aicomputer
else
npm install -g aicomputer
COMPUTER=computer
fi
$COMPUTER whoami || $COMPUTER login
Fleet control
Discover machines and agents
$COMPUTER ls --json
$COMPUTER agent agents <machine> --json
Sessions
Create, reuse, and manage named sessions on a machine:
$COMPUTER agent sessions new <machine> --agent claude --name research --json
$COMPUTER agent sessions list <machine> --json
$COMPUTER agent status <machine> --session <session_id> --json
Prompting and monitoring
$COMPUTER agent prompt <machine> "<task>" --agent claude --name research
$COMPUTER agent watch <machine> --session <session_id>
Stopping and cleanup
$COMPUTER agent cancel <machine> --session <session_id> --json
$COMPUTER agent interrupt <machine> --session <session_id> --json
$COMPUTER agent close <machine> --session <session_id>
Research delegation workflow
- Pick a machine:
$COMPUTER ls --json - Create a session:
$COMPUTER agent sessions new <machine> --agent claude --name research --json - Send a self-contained research prompt:
$COMPUTER agent prompt <machine> \
"Run a deep research workflow on <topic>. Write all outputs to /workspace/outputs/. When done, write a summary to /workspace/outputs/summary.md." \
--agent claude --name research
- Monitor:
$COMPUTER agent watch <machine> --session <session_id> - Retrieve:
$COMPUTER agent prompt <machine> "cat /workspace/outputs/summary.md" --session <session_id> - Clean up:
$COMPUTER agent close <machine> --session <session_id>
ACP bridge
Expose a remote machine agent as a local ACP-compatible stdio process:
$COMPUTER acp serve <machine> --agent claude --name research
This lets local ACP clients (including Feynman's subagents) talk to a remote agent as if it were local. Keep the bridge process running; reconnect by restarting the command with the same session name.
Session naming
Use short stable names that match the task:
research— general research delegationexperiment— autoresearch loopsreview— verification passesliterature— literature sweeps
Reuse the same name when continuing the same line of work.
References
- CLI cheatsheet — full command reference
- ACP flow — protocol details for the ACP bridge