Workflow guides: drafting, sharing, memory and moving work
How onecell fits together for everyday jobs: a document from draft to published, organising cells, keeping facts, sharing with a team, and moving work.
Each guide shows what to ask your agent and what happens in onecell. For one-prompt jobs (a Monday brief, a postmortem, a launch post), see the recipes.
From draft to published
Ask for a draft
“Write up what we decided about retries, in the backend cell.” The agent searches first, then creates a draft. Leave out the cell and it goes to your Inbox.
Read it in onecell
Edit it yourself, or ask the agent to change it. Every save is a version you can go back to.
Publish when it is right
Publishing checks a little more strictly: a title, a one-line summary and enough text to stand on its own. If it refuses, it says what to fix.
Organising cells
- One cell per project, client or topic you would share as a unit. Who can see a cell is decided per cell, so group by audience, not by format.
- Put what the whole team needs on the hive; keep drafts and half-formed notes in your Inbox.
- Nest a document under another to keep a series together. It moves with its parent.
- Pin the cells you open every day; the rest sit under Cells in the sidebar.
Keeping facts
Some things are one sentence, not a document: “Acme renews on 1 March”, “we use Postgres for the job queue”. Ask your agent to remember it, in a cell or your Inbox. Later, it recalls the fact before it answers, and you see the same list on the cell page.
When something changes, the agent retires the old fact and remembers the new one. The old one stays in the history, so you can still see what you believed before.
Sharing with a team
| You want | Do this |
|---|---|
| Everyone in your team to see it | Put it on the hive |
| One or two people to see a cell | Share the cell with them as viewer or editor |
| Everyone in your cluster, now and later, to see a cell | Open the cell to the cluster, as viewer or editor |
| Someone outside the team to read one page | Make a read-only link to the published document |
| Anyone on the web to read it | Make it public, and it gets its own address |
A viewer reads what is published; an editor also sees drafts and can change them. Your Inbox cannot be shared in any of these ways.
Moving work
Where a document lives decides who sees it, so moving is always your call. Ask: “Move the pricing notes to the strategy cell.” The agent shows what would move (including anything nested under it), says if anyone would lose access, and moves it only when you say yes.
When a whole project spins out into its own team, move the cell to another cluster instead: its documents, memory and links go together.