Rename .pi to .feynman, rename citation agent to verifier, add website, skills, and docs

- 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>
This commit is contained in:
Advait Paliwal
2026-03-23 17:35:35 -07:00
parent 406d50b3ff
commit f5570b4e5a
98 changed files with 9886 additions and 298 deletions

View File

@@ -0,0 +1,108 @@
---
name: agentcomputer
description: 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.
allowed-tools: 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
- `/autoresearch` or `/deepresearch` should 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:
```bash
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
```bash
$COMPUTER ls --json
$COMPUTER agent agents <machine> --json
```
### Sessions
Create, reuse, and manage named sessions on a machine:
```bash
$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
```bash
$COMPUTER agent prompt <machine> "<task>" --agent claude --name research
$COMPUTER agent watch <machine> --session <session_id>
```
### Stopping and cleanup
```bash
$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
1. Pick a machine: `$COMPUTER ls --json`
2. Create a session: `$COMPUTER agent sessions new <machine> --agent claude --name research --json`
3. Send a self-contained research prompt:
```bash
$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
```
4. Monitor: `$COMPUTER agent watch <machine> --session <session_id>`
5. Retrieve: `$COMPUTER agent prompt <machine> "cat /workspace/outputs/summary.md" --session <session_id>`
6. Clean up: `$COMPUTER agent close <machine> --session <session_id>`
## ACP bridge
Expose a remote machine agent as a local ACP-compatible stdio process:
```bash
$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 delegation
- `experiment` — autoresearch loops
- `review` — verification passes
- `literature` — literature sweeps
Reuse the same name when continuing the same line of work.
## References
- [CLI cheatsheet](references/cli-cheatsheet.md) — full command reference
- [ACP flow](references/acp-flow.md) — protocol details for the ACP bridge

View File

@@ -0,0 +1,23 @@
# 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.

View File

@@ -0,0 +1,68 @@
# CLI Cheatsheet
## Authentication
```bash
computer whoami
computer login
computer claude-login # install Claude credentials on a machine
computer codex-login # install Codex credentials on a machine
```
## Machine discovery
```bash
computer ls --json
computer fleet status --json
```
## Agent discovery
```bash
computer agent agents <machine> --json
```
## Sessions
```bash
computer agent sessions list <machine> --json
computer agent sessions new <machine> --agent claude --name research --json
computer agent status <machine> --session <session_id> --json
```
## Prompting
```bash
computer agent prompt <machine> "run the experiment" --agent claude --name research
computer agent prompt <machine> "continue" --session <session_id>
```
## Streaming and control
```bash
computer agent watch <machine> --session <session_id>
computer agent cancel <machine> --session <session_id> --json
computer agent interrupt <machine> --session <session_id> --json
computer agent close <machine> --session <session_id>
```
## ACP bridge
```bash
computer acp serve <machine> --agent claude --name research
```
## Machine lifecycle
```bash
computer create my-box
computer open my-box
computer open my-box --terminal
computer ssh my-box
```
## Good defaults
- Prefer machine handles over machine ids when both are available.
- Prefer `--name` for human-meaningful persistent sessions.
- Prefer `--json` when another program or agent needs to read the result.

View File

@@ -0,0 +1,12 @@
---
name: autoresearch
description: Autonomous experiment loop that tries ideas, measures results, keeps what works, and discards what doesn't. Use when the user asks to optimize a metric, run an experiment loop, improve performance iteratively, or automate benchmarking.
---
# Autoresearch
Run the `/autoresearch` workflow. Read the prompt template at `prompts/autoresearch.md` for the full procedure.
Tools used: `init_experiment`, `run_experiment`, `log_experiment` (from pi-autoresearch)
Session files: `autoresearch.md`, `autoresearch.sh`, `autoresearch.jsonl`

View File

@@ -0,0 +1,12 @@
---
name: deep-research
description: Run a thorough, source-heavy investigation on any topic. Use when the user asks for deep research, a comprehensive analysis, an in-depth report, or a multi-source investigation. Produces a cited research brief with provenance tracking.
---
# Deep Research
Run the `/deepresearch` workflow. Read the prompt template at `prompts/deepresearch.md` for the full procedure.
Agents used: `researcher`, `verifier`, `reviewer`
Output: cited brief in `outputs/` with `.provenance.md` sidecar.

10
skills/jobs/SKILL.md Normal file
View File

@@ -0,0 +1,10 @@
---
name: jobs
description: Inspect active background research work including running processes, scheduled follow-ups, and pending tasks. Use when the user asks what's running, checks on background work, or wants to see scheduled jobs.
---
# Jobs
Run the `/jobs` workflow. Read the prompt template at `prompts/jobs.md` for the full procedure.
Shows active `pi-processes`, scheduled `pi-schedule-prompt` entries, and running subagent tasks.

View File

@@ -0,0 +1,12 @@
---
name: literature-review
description: Run a literature review using paper search and primary-source synthesis. Use when the user asks for a lit review, paper survey, state of the art, or academic landscape summary on a research topic.
---
# Literature Review
Run the `/lit` workflow. Read the prompt template at `prompts/lit.md` for the full procedure.
Agents used: `researcher`, `verifier`, `reviewer`
Output: literature review in `outputs/` with `.provenance.md` sidecar.

View File

@@ -0,0 +1,12 @@
---
name: paper-code-audit
description: Compare a paper's claims against its public codebase. Use when the user asks to audit a paper, check code-claim consistency, verify reproducibility of a specific paper, or find mismatches between a paper and its implementation.
---
# Paper-Code Audit
Run the `/audit` workflow. Read the prompt template at `prompts/audit.md` for the full procedure.
Agents used: `researcher`, `verifier`
Output: audit report in `outputs/`.

View File

@@ -0,0 +1,12 @@
---
name: paper-writing
description: Turn research findings into a polished paper-style draft with sections, equations, and citations. Use when the user asks to write a paper, draft a report, write up findings, or produce a technical document from collected research.
---
# Paper Writing
Run the `/draft` workflow. Read the prompt template at `prompts/draft.md` for the full procedure.
Agents used: `writer`, `verifier`
Output: paper draft in `papers/`.

View File

@@ -0,0 +1,12 @@
---
name: peer-review
description: Simulate a tough but constructive peer review of an AI research artifact. Use when the user asks for a review, critique, feedback on a paper or draft, or wants to identify weaknesses before submission.
---
# Peer Review
Run the `/review` workflow. Read the prompt template at `prompts/review.md` for the full procedure.
Agents used: `researcher`, `reviewer`
Output: structured review in `outputs/`.

View File

@@ -0,0 +1,14 @@
---
name: replication
description: Plan or execute a replication of a paper, claim, or benchmark. Use when the user asks to replicate results, reproduce an experiment, verify a claim empirically, or build a replication package.
---
# Replication
Run the `/replicate` workflow. Read the prompt template at `prompts/replicate.md` for the full procedure.
Agents used: `researcher`
Asks the user to choose an execution environment (local, virtual env, cloud, or plan-only) before running any code.
Output: replication plan, scripts, and results saved to disk.

View File

@@ -0,0 +1,10 @@
---
name: session-log
description: Write a durable session log capturing completed work, findings, open questions, and next steps. Use when the user asks to log progress, save session notes, write up what was done, or create a research diary entry.
---
# Session Log
Run the `/log` workflow. Read the prompt template at `prompts/log.md` for the full procedure.
Output: session log in `notes/session-logs/`.

View File

@@ -0,0 +1,12 @@
---
name: source-comparison
description: Compare multiple sources on a topic and produce a grounded comparison matrix. Use when the user asks to compare papers, tools, approaches, frameworks, or claims across multiple sources.
---
# Source Comparison
Run the `/compare` workflow. Read the prompt template at `prompts/compare.md` for the full procedure.
Agents used: `researcher`, `verifier`
Output: comparison matrix in `outputs/`.

12
skills/watch/SKILL.md Normal file
View File

@@ -0,0 +1,12 @@
---
name: watch
description: Set up a recurring research watch on a topic, company, paper area, or product surface. Use when the user asks to monitor a field, track new papers, watch for updates, or set up alerts on a research area.
---
# Watch
Run the `/watch` workflow. Read the prompt template at `prompts/watch.md` for the full procedure.
Agents used: `researcher`
Output: baseline survey in `outputs/`, recurring checks via `pi-schedule-prompt`.