Working folder vs artifacts
Open in product: preshos.com/agent-ops/working-folder
A session keeps two kinds of file state. The working folder is live scratch space: intermediate files, drafts-in-progress, tool outputs, and anything the agent needs along the way. The Workspace holds durable artifacts: the pages, files, and deliverables the session presents for human eyes. Knowing which is which keeps review on the artifact and experimentation in the folder.
The split
Section titled “The split”| Working folder | Workspace artifacts |
|---|---|
| Live and disposable | Durable and reviewable |
| Agent’s scratch state | Member-facing outputs |
| Safe to overwrite and discard | Versioned by content hash, with the record behind them |
| Never the deliverable | The deliverable, or its draft |
Working rules
Section titled “Working rules”- Review artifacts, not folder contents. The preview pane shows what the agent stands behind; the folder shows how it got there.
- A file nobody was asked to review is not approved. Pulling a working-folder file into downstream work skips the review the artifact path would have given it.
- Promote deliberately: when scratch work becomes worth keeping, it becomes an artifact through the session — not by copying paths around it.
- Secrets never land in either. Credential values stay in the vault and arrive as grants; they are never written into folder files, artifacts, chat, or code.
What next
Section titled “What next”- Artifact versions: how reviewable outputs iterate.
- Sandbox: the isolated space both live inside.
- Approving agent actions: reviewing what the agent presents.