Saving a sub-agent's output as a document in a project folder

Specialist output doesn't have to live only in the chat. When Camelia delegates with spawn_subagent, the result can be saved as a document into a project folder you choose, turning a brief, analysis, or plan into a durable artifact.

How saving works

The spawn_subagent handoff returns the specialist's markdown, and that result can optionally be written as a document into a chosen project folder. Documents are stored in your project's encrypted folder backbone in Cloudflare D1, so a saved sub-agent output behaves like any other file: viewable, editable, movable, and deletable in the Documents section.

Smart labels in flows

When sub-agents run as flow steps, each step can save its artifact with a smart label derived from the role — for example Research, Analysis, Design, Spec, Legal, or Manufacturing for role steps (and "Integration" for MCP steps). That makes it easy to scan a folder and see which specialist produced what.

Encryption at rest

Saved documents are encrypted at rest with AES-GCM, with per-project key separation and a server-only key. This is operator-decryptable envelope encryption — the key never reaches the browser — not zero-knowledge or end-to-end encryption.

Working with saved outputs

Once saved, sub-agent documents flow into the rest of the project. They can be organized or relabeled with Camelia's Organize and Smart Label tools in Documents, fed forward as context to later flow steps, or bundled into deliverable packs in Outputs. A manufacturing sourcing plan or a research brief saved this way becomes part of the project's working record, not just a transient chat message.

If you want output saved, just tell Camelia where it should go, or let her pick an appropriate backbone folder.