A shared space for your business.
Keep customer work, tasks, decisions and agent handoffs together. Start with your business workspace, then choose who can join each space.
Use managed LogMem
Invite onlyFor solo operators and small teams. We manage storage. You do not need a Redis account or connection URL.
- Sign in with the email that received access.
- Create your business workspace, or join your team through its invitation link.
- Choose a private space and connect one agent.
- Add a real task and check its first update.
Already have a team invitation link? Open that link to join the right workspace.
Managed access is invite only. Public signup is not open.
No invitation yet? .
Bring your own Redis
AdvancedFor developers who manage their own storage and agent configuration.
- Works with Upstash, a TLS Redis, or an HTTPS REST bridge.
- Name your space and run a read-only connection test.
- Get ready-to-paste config for Claude, Cursor, Codex and more.
What would you use it for?
Pick the one closest to you. Include this with your access request. This form does not create an account or workspace.
Find the AI tools on this machine.
Run this in a terminal. It looks for 9 agent tools on your PATH, prints what it finds, and sends only their names and versions back to this page.
- Read-only: it checks which commands exist and runs
--versionon each, 3 seconds at most. - It never reads config files or environment variables, and sends nothing without the code.
- The code
works once. The result is deleted after 10 minutes.
Join the waitlist.
Managed access is invite only. Leave your email to request access. Already invited? Go back and open your workspace with your approved email.
Signing up again with the same email only updates your answer and agent count. Want it today? .
Name your space.
A space is one walled-off memory: one team, one client, or one project. Agents connected to it can’t read any other space.
Connect your Redis.
LogMem stores everything in a Redis you control. The test sends three read-only commands: PING, then TYPE and EXISTS on a random key that doesn’t exist. It writes nothing.
Your URL and token go to /api/onboarding/test once, are used for those three commands, and are dropped. This page doesn’t save them: they go into your agent’s own config in the next steps. Private and internal addresses are refused.
Bring your existing agent history?
If your agents already use the ACMI protocol, compatibility mode lets them keep their acmi_* tools and shows their history in LogMem. Turn it off if you’re starting fresh.
Connect your first AI tool.
Pick the tool. Paste the snippet, restart it, and its first call starts with a short catch-up.
<space token>.OPTIONAL, AFTER SETUP
Watch the first notes arrive.
Ask your agent: logmem start quill, then give it any small task. As it works, it writes notes on what changed, in order. Below is what that looks like.
When work stops, the agent leaves a recap. If it forgets, LogMem writes one after 30 minutes of quiet, so the next catch-up is never empty.
Add a second agent and hand it work.
Shared memory pays off when work moves between agents. Connect one more, then ask quill to hand something to it. The handoff stays open until the other agent picks it up.
- Repeat on another host, with
LOGMEM_AGENT=atlas. - Tell quill:
hand issue 14 to atlas. LogMem writes a Handoff and atlas follows the job. - atlas’s next Brief lists the Handoff until it notes
accepted.
Invite a person to approve.
Some actions can’t be undone: sending, paying, deleting, publishing. Before one of those, the agent stops and shows this person the exact action. They see it under Decisions and approve or reject it; then the agent carries on. (Today the agent waits on its own; enforcement on our side is coming.)