One home for every AI coding tool you use. Every session on your Mac, and one memory they all share.
curl -fsSL https://uniloom.dev/install.sh | bashWorks with and 11 more
Sessions shows every AI session on your computer, by project and branch: who is working, who is waiting on you. A session can hand work to other agents, each on its own branch, and every plan or question still comes to you.
Under your own sign-in. The first six are verified end to end; the ten newest are in Beta.
Inside the agent you already use
Uniloom is an MCP server. Each connected agent calls recall when it needs context and remember when it learns something. The memory comes to the terminal you already work in.
> add the totals to the checkout page ⏺ uniloom - recall (MCP)(query: "checkout setup") ⎿ 1 memory · "Use pnpm in Atlas, not npm" saved Monday, from a Claude Code session ⏺ I'll follow that and add the totals.
Why Uniloom
Each session starts blank. What Claude Code worked out on Tuesday, Cursor has never heard of on Wednesday — so you explain it again.
Sessions run in different tools and folders. The one that stopped to ask you a question has been sitting there for twenty minutes.
Standups, reviews, the ticket you owe a reply. None of it happens unless you do it, and none of it is the work you sat down to do.
Uniloom fixes it the way your own memory works: it notices, remembers, recalls and acts — for every agent at once, on your computer, in files you own.
Every session from every agent is captured as it happens, from the transcripts the tools already write. Nothing to remember to do, nothing to paste.
Decisions with their reasons, preferences, lessons, where each branch stands — each tied to the file it's about, and flagged when that code changes.
When any tool starts a task, the right memory is already there — whichever tool you open next. Not when you think to ask: when the work needs it.
Automations run your standup, debrief each session and draft the reply you owe — on the agent you already pay for, inside rules you set.
Why "Uniloom"? A loom takes many separate threads and weaves one cloth. Your agents are the threads.
Sessions1 of 5
Uniloom reads the transcripts your agents already write, so every session on your computer shows up on its own, grouped by project and branch. Nothing to install in each tool.

Memory2 of 5
Uniloom is an MCP server. Your tools recall at the start of a task and remember at the end — decisions with their reasons, preferences, lessons — into the same workspace.

Toolkit3 of 5
Every agent wants its instructions and skills in its own place and format. Toolkit keeps one copy — in AGENTS.md and .uniloom/ — and keeps every connected agent in sync with it.

Automations & Tasks4 of 5
Tasks gathers what you owe — issues, reviews and replies from GitHub, Linear, Jira and Slack, beside your own to-dos. Automations work through it: a standup at 7:00, a debrief when a session ends, a plan for each new ticket, on the agent you already pay for.

Widgets & Artifacts5 of 5
Any connected tool can publish a chart, a report or a page to Uniloom, and every change you ask for becomes a new version. Need more? Describe a small widget and watch your agent build it, beside the chat that made it.

Typed pages — plan, design, bug report — under the project and branch they belong to, in a real block editor.
Sessions, time and tokens across every tool, by project and branch — and what Uniloom learned on the way.
What needs you, one card at a time — and one box to ask anything, on the agent you already use.
Getting started
One command downloads Uniloom, checks it and opens it. About thirty seconds — no Homebrew, no Node, nothing to build.
Sign in once with Google or GitHub. Then a 4-step setup you can skip — Welcome, Agents, Integrations, Project — connects the agents you use and opens on Sessions. Uniloom asks before it touches any tool's config.
Use your tools as you always do. Sessions are captured, memory grows, and Home tells you what needs you.
Why Uniloom is different
Both are off. Nothing is sent unless you turn one on.
Neither ever includes your docs, your conversations, or any file path.
Questions
Free for individuals. Team plans are coming. There is no licence key or trial to activate. What you have written stays yours either way: it lives in files on your computer.
A Mac — Apple Silicon or Intel — and at least one of the 16 AI coding CLIs Uniloom supports, such as Claude Code, Codex, Cursor or GitHub Copilot, already signed in.
The Mac needs macOS 13.5 or later, on Apple Silicon or Intel; each has its own download. Linux and Windows are early builds. You also sign in to Uniloom once, with Google or GitHub.
No. Uniloom reads the transcripts your tools already write and keeps them on your computer. Your agent still talks to its own model under its own sign-in, as it always did. A workspace you choose to share is readable by its members. Personal is not shared unless you turn its sharing on. Every exception, precisely.
Nothing until you connect one. Connecting installs Uniloom into that tool: as a plugin where the tool takes one, such as Claude Code, Codex, Gemini and Cursor, and through its own config file otherwise, such as OpenCode. A config file Uniloom changes is copied aside first, and turning a tool off takes out what Uniloom put there.
curl script and not a .dmg?Uniloom is not notarized by Apple yet. macOS quarantines anything a browser downloads, and for an un-notarized app that becomes a "could not verify" dialog you can only clear in System Settings. curl sets no quarantine flag, so the app simply opens. The script is short and commented — read it first.
The download against the release's SHASUMS256.txt — which catches a corrupted download, not a compromised host, since both come from the same place. Updates are stronger: each is signed, and Uniloom checks the signature against a key built into the app before installing.
# check a download yourself
shasum -a 256 -c SHASUMS256.txt
Uniloom checks while it is open, downloads a new version in the background and installs it when you next quit. Nothing restarts on its own.
One command takes Uniloom out of every agent it was connected to and removes the app. Your workspace is kept unless you ask otherwise, and --dry-run shows every step first.
curl -fsSL https://uniloom.dev/uninstall.sh | bash -s -- --dry-run
Yes, optionally. A shared workspace is a separate file that its members read; your Personal workspace stays private unless you share it. Each page has one author and opens read-only for everyone else. Team plans are coming.
One command. About thirty seconds. Sign in once. Your work never leaves your Mac.
curl -fsSL https://uniloom.dev/install.sh | bash