Ark OS
For Claude Code

Your team's memory,
inside your assistant.

One install. One sign-in. Claude Code gets what your team already knows, your private workspace, your data and a cloud worker that keeps going after you close the laptop.

$curl -fsSL https://ark-os.co/mcp/install | sh

Then, in Claude Code: /mcp → ark → sign in with your work email and access key. That's it.

1

Install

The command above adds the Ark plugin to Claude Code. Nothing else to configure.

2

Sign in

Type /mcp, pick ark, sign in once in the browser. Same email and key as your Ark seat.

3

Work

Every new session opens with your team's memory in it and logs itself back to the team when it ends.

How it works

Ark is not another app to open. It is the layer under every seat: one memory, one private repo, one datastore, one worker — reached from the tools you already use.

Claude Codeon your machine
→
Arksign-in · memory · files · data
→
Your cloud workerjobs · schedules · always-on agent
what did we decide about the Q4 pricing for corporate orders?
recall("Q4 pricing corporate orders")
Sept 12 — minimum order $2,500 for corporate accounts, 15% off above $10k (decided by the ops lead). The Q4 goal is $700k, so the sales sheet leads with the volume tier.
good. remember that the owner wants the volume tier shown only when the customer asks.
remember("Corporate volume tier — show only when asked", …)
Saved to team memory. Everyone on the workspace sees it from their next session.

What you get

Plain tools with plain names. Claude picks them up on its own; you just talk.

Shared memory

Decisions, preferences, customers, gotchas — saved once, known by every seat. Ark also learns from finished sessions on its own, and every fact says who taught it.

recall · remember · memories · forget

Private workspace

Your team's own repo, handled the GitHub way: read, search, write. Writes are commits under your name, and the cloud worker sees them instantly.

files · read_file · write_file · search_files · history

Cloud worker

Run long jobs in the background, schedule recurring ones, or hand a task to the always-on Ark agent that has your whole workspace and skills.

run · job · schedule · automations · ask_agent

Your data, your record

A Postgres datastore that is yours. Every Claude Code session is logged back — who did what, what it cost — visible to the team, not to anyone else.

query · sessions · usage · team

Questions

Do I need an Ark account?

Yes — a seat on your team's workspace. Your welcome email has your access key. Lost it? The sign-in page can email it to you.

Where does my data live?

In your team's own database and private repo on Ark's servers, separate from every other team. Sign-in and revoke are the same as for the rest of your Ark seat.

What does it log?

Your Claude Code sessions (the conversation and token usage) go to your team's record so the team can see the work and what it cost. Nothing is sent anywhere else.

Does it work with other assistants?

Ark speaks MCP with OAuth, so any assistant that supports remote MCP servers can connect to https://mcp.ark-os.co/mcp. The one-line installer is for Claude Code.

How do I remove it?

In Claude Code: /plugin uninstall ark@ark-os. Your team's memory stays with the team.