PhiCo
PhiCo is the composer. You say what you want, PhiCo proposes a Receipt — the line-numbered account of what would change — and you accept, modify or reject it. Nothing publishes without an accepted Receipt.
PhiCo composes against the live block catalog, so a proposal only ever contains blocks your World actually has.
Two ways to talk to it
| Mode | What it does |
|---|---|
| Compose | Builds and changes. Produces a Receipt: new pages, added sections, edited properties, wired data, theme changes. |
| Chat | Answers. Asks what you meant, explains what a page does, thinks through an idea — without touching the app. |
Start a new thread whenever the subject changes; each thread keeps its own
conversation, and Cmd/Ctrl+K puts you back in the composer input.
What PhiCo can and can’t see
PhiCo composes from the live block catalog plus the short brief each block ships with — what it is for, when to use it, when not to, and what people get wrong about it. It does not see your World’s private data, your email, or anything outside the current session unless you deliberately bind a data source.
Each World can override those briefs on its own installed blocks, which is useful when your vocabulary differs from ours.
Φ accounting
Φ is spent as PhiCo works: each turn costs credits based on the work it produces. Opening a thread is free, and accepting or rejecting a proposal costs nothing by itself — the proposal was paid for when it was generated.
When the wallet empties mid-month, add Φ from the Wallet page of your account. A new cycle refills at the start of the next billing period.
Where you can reach it
- In the product — the composer pane, alongside the canvas.
- From your terminal — the PhiCo Code plugin for Claude Code.
- Over REST —
POST /api/ai/composer/stream, see AI integration.
See also
- Receipts — what PhiCo proposes
- Surfaces — what PhiCo composes against
- AI integration — models, custom agents, the API