From install to your first saved conversation
About five minutes. You install one plugin, link your computer once, connect the Claude account you use, and from then on everything is a sentence in the chat — no command line.
Before you start
- Node 20 or newer on your PATH. The plugin starts its program with
npx. Without Node it installs cleanly and then has no tools — which looks like a broken plugin rather than a missing runtime. - An Actario account. Create one with email, Google or GitHub. Linking signs you in through the browser; there is no token to copy.
node --versionInstall the plugin
Pick the Claude you use. The plugin is the same everywhere it can run; the program it starts is fetched from npm on first run, so there is nothing to clone and no path to configure.
Claude Code
RecommendedAdd the public marketplace, then install:
/plugin marketplace add actario/actario-plugin
/plugin install actario@actarioClaude desktop app · Cowork
By file for nowThe desktop app installs plugins from marketplaces your Claude account already has, and does not yet offer a way to add a new one. Until Actario is listed in the plugin directory, ask us for the actario.plugin file and add it from the app’s plugin settings. Once installed it works fully — including from a Cowork cloud session, because its tools run on your computer.
claude.ai on the web or phone
Connector onlyNo plugin can run there. Skip to step 3 and add the connector: you can find and bring back conversations, load memories and manage masked shares. Capturing, real values and sealed shares stay on a computer with the plugin.
Link this computer
In any chat, say:
link my machine to Actario- A browser tab opens. Sign in, check that the code matches the one in the chat, pick a workspace, approve.
- The computer is registered as a source under its hostname. You do this once per computer.
https://actario.app/link on any device, sign in, and enter the code.~/.actario, the others in ~/.actario/profiles/), and every call goes to the home of whoever’s Claude account made it.Connect your AI account
Linking binds the computer to your Actario account. On its own that would let any Claude account on the computer act as you — so each AI account also connects itself, once. The plugin answers only an account that is connected to the same Actario account as the computer.
https://actario.app/api/mcpclaude.ai · desktop app
- Open Settings → Connectors → Add custom connector.
- Paste the URL above, sign in to Actario, approve.
Claude Code
claude mcp add --transport http actario-account https://actario.app/api/mcpCheck it works
run Actario’s doctorIt lists which conversation sources this computer has and whether they parse. Then save your first one:
save this conversation to ActarioUsing Actario
Everything is a sentence. These are examples — say it the way you would say it.
save this conversation to ActarioWrites a faithful record, redacts it, uploads it, then your agent cuts it into topic segments and writes the note page. You get a link to it on the web.
continue the conversation about the LOPO splitClaude finds the run, downloads it to your machine and starts from its note page, segments and latest turns. What comes back is the conversation, not the computer: file contents, diffs, attachments, tool output past 8 KB and the real values behind pseudonyms were never uploaded, so they are not restored.
build a memory of the B1 work since SeptemberDownloads those conversations and compacts them on your machine, with your own model, into one memory — goal, status, to-do, conventions, files and commands — every line linked to where it came from. It stays local unless you ask to upload it.
share this conversation with mei@example.comMakes a masked link only she can open, after signing in. 30 days by default, revocable, with a list of who opened it. Real values only when you ask, and only to your organization or named people.
tell the frontend agent the /runs response now has turns_countSends it, encrypted, to your frontend line; that session sees it in its inbox. A command is never carried out until you approve it on the receiving side. In preview, between your own agents only.
On the web
Sign in to see what your agents saved. The summaries are written by your own agent; the web shows them and lets you edit them.
| Page | What it is for |
|---|---|
| Agents | What each line of work is on, its latest runs, and how fresh the captured data is. |
| Runs | Every uploaded conversation; open one for its note page (editable, exports to Markdown) and the original turns. |
| My shares | Links you have shared, who opened them, revoke. |
| Connected AI accounts | The AI accounts you have connected; disconnect one here. |
| Messages | Message envelopes, the computers that can read your messages, revoke a computer (preview). |
| Settings | Workspace, sources, tokens and plan. |
Data & privacy
Redaction happens in the program on your computer, before upload, and cannot be switched off. Keys, tokens, email addresses and the account name in your home-folder paths are always replaced. You can only add to it:
{
"redaction_terms": ["Acme Corp", "Project Falcon"]
}What stays on your computer
- The pseudonym salt and map.
actario unmaskreverses an export locally — the only way it can be reversed at all. - Restored conversations (
~/.actario/restore/) and memories (~/.actario/memory/), masked as uploaded. Real values shown on request are never written there. - This computer’s message key (
~/.actario/keys/), readable by your OS account only. The private half never leaves it.
Shares that show real values
Only from the computer that captured the conversation: the content is encrypted there and the key travels in the link’s #k= part, which no server sees. Keys, tokens and your redaction_terms are never shown, even then.
Updating
Claude Code refreshes marketplaces shortly after a session starts and updates installed plugins in place. To force it:
/plugin marketplace update actario
/reload-pluginsTroubleshooting
The plugin installed, but there are no Actario tools
Most often Node is missing or older than 20 — check node --version. If Node is fine, the server was announced but not yet read: ask the client to refresh its tool list, run /reload-plugins in Claude Code, or start a new session.
It worked yesterday; today nothing answers
You are probably in a different Claude account. Connect that account too (step 3), or check Connected AI accounts.
My conversation went to the wrong line of work
A chat inside a Cowork or claude.ai Project is captured under that project’s line; a restored conversation captured again is offered the line it came from. Anything else lands in the unbound queue on the Agents page, where you can assign it.
A new computer cannot read my agent messages
The first computer is approved automatically; each later one waits until you approve it from a computer that already is. That step runs in a terminal: actario agent trust, which asks for the new computer’s 20-character fingerprint.
Something else
Run the doctor first and include its output when you open an issue on GitHub.