Say it once: Octuo recalls what you told it
It is Monday, you open a fresh chat, and you paste in the same project background you pasted last week: who the client is, what was decided, how the weekly update should read. Say it once and Octuo can recall what you've told it anywhere in your account, so a new conversation does not start from zero. When it hands a job to another tool, the context that job needs goes along with it.
What Octuo does at that moment
- It recalls across sessions. What you have said anywhere in your account is available to Octuo as context, so you do not have to repeat yourself in each new chat. Not every remembered item is used in every task.
- You can look at it. Memory is a graph you can browse, edit, or tell Octuo to forget. The memory module on the Canvas lets you view and manage what the agent can recall.
- Tasks carry forward. A task keeps its context across sessions, so it survives the end of a conversation.
- The context travels with the job. When Octuo delegates work to a supported tool or agent, it carries the context that job needs and brings the results back.
- You step in less. Octuo does the preparing, handing over and following up. You step in for your own account sign-ins, payments and sensitive approvals that must be yours.
Three examples
These are illustrative situations, not customer stories.
A weekly update you explained once
A consultant tells Octuo once who reads her weekly client update, which sections it has and how formal it should sound. The following week she asks for the new update without restating any of that, and Octuo works from what it recalls. She reads the draft, fixes a line that is out of date, and decides whether it goes out.
A coding task that starts with the decisions in hand
A founder asks Octuo to hand a bug fix to Codex or Claude Code. The project's naming and the decisions from earlier conversations were already told to Octuo, so the brief it writes includes the parts the fix depends on. The coding tool keeps its own history and Octuo does not import it; the founder signs in to their own account for that tool and reviews what comes back.
Opening the memory to see what it holds
Before starting a new project, a designer opens the memory module and reads what Octuo has on file. One line is stale, so she edits it. Another note is about work she no longer wants kept around, so she tells Octuo to forget it. If she wants a routine for this, our ten-minute monthly review is one way to do it.
What it does not do
Octuo is not a perfect record of everything you have ever said. Memory is context it can draw on, so not every remembered item is used in every task. The memory module shows what the agent can recall, not full prompts or internal reasoning, and Octuo does not import the chat histories that Claude Code and Codex keep for themselves.
FAQ
Does it really remember across chats, or do I still have to repeat myself? Octuo can recall what you've said anywhere in your account, across sessions, so you do not need to paste the same background into every new chat. It is context it draws on, so if something matters for a job, you can check that it is there. If you would rather build a note by hand first, here is how to get an assistant to remember what you told it.
Can I see and edit what it remembers? Yes. Memory is a graph you can browse and edit, and you can tell Octuo to forget something. The memory module lets you view and manage what the agent can recall; it is not a viewer for full prompts or the model's internal reasoning.
Is that memory shared with Claude Code or Codex? Not as one shared memory: each of those tools keeps its own history. When Octuo hands work to a supported tool, it carries the context the task needs, and it does not import the vendor's own chat history.
See what Octuo does. Octuo is in public beta on macOS and web, and an iPhone app is coming soon. New accounts get 1,000 OC trial credits, once per person, no card.
The product names above belong to their owners. We have no affiliation with them.