onecell

Sign in

Help

I want to …

Pick a job. Each one is a single prompt for your agent: it reads what onecell already knows, does the work, and leaves the result where your team will find it.

All 20 recipes, by role →By role:DevelopersMarketingCustomers & supportResearch & productFounders & operators

Getting started

  1. Connect the AI you useChatGPT, Claude, or a coding tool. A few minutes, with a check that it worked.
  2. Run your first recipeThe result lands as a draft in your private Inbox.
  3. Share a cell with your teamPublish in the team space, or open a cell to your whole team.
Set up your AI, step by stepEvery agent's setup →Read the full guide →

Documentation

Agent hooks: onecell in Claude Code and Codex, unaskedHooks let onecell bring up relevant memory, brief a new session and suggest saving what a turn settled. Off until you turn them on; nothing you type is stored.Artifacts: what your agent can make in onecellDiagrams, charts, timelines, decisions, tables, diffs and small interactive tools, made by your agent as real blocks you can read, edit, search and share.Automations: let your tools write to onecellGitHub Actions, n8n, Zapier, cron jobs: anything that can call MCP or send an HTTP request can keep its work in onecell, as memory your team can find.Concepts: cells, clusters, the hive and your InboxThe few ideas onecell is built on: documents and blocks, cells, your private Inbox, clusters and the hive, memory, search with citations, and decisions.Tool reference: every onecell MCP tool, by areaEvery tool onecell gives your agent, grouped by area, with what it does and which ones a Drafts only key can use. Every change runs as a dry run first.Workflow guides: drafting, sharing, memory and moving workHow onecell fits together for everyday jobs: a document from draft to published, organising cells, keeping facts, sharing with a team, and moving work.