Skip to main content
Ask it to “get the alicein context” explicitly. If it says it has no such tool, the connection is not registered: check that .mcp.json exists in the folder you started the session from, and restart the session — Claude Code reads it at startup.
You do not get a separate token. Open alicein.app/start. After Google, Connect shows one command that already carries it. Copy that command. If the page says it cannot reach Alice.In, wait a minute and refresh — there is nothing to paste until the command appears.
Run the install command from your project’s folder rather than your home directory, and make sure your agent is installed and signed in first. The installer needs Node 18 or newer and says so if it is missing. On Windows, use the PowerShell line from the Connect page (or the Windows tab), not curl … | sh.
The token lives in .claude/alice/config.json, not in .mcp.json — a helper command reads it when your agent connects. That needs Claude Code 2.1.193 or newer. On an older build, reinstall with the fallback that writes the token into .mcp.json directly, and keep the repo private.
It was given a repository name where it needed a path to a checkout on your machine, or that repo is not cloned here. Either clone it and run the reading step again, or leave it out and tell your agent about it in the interview — but do not let an unread repo pass as a small one.
A save needs the exact text shown to you in the last half hour. If you asked for a change after approving, your agent must show the new version first. If the workspace already has real content, seeding will not overwrite it; things get added one at a time.
The queue is a pull model, on purpose. Nothing runs until you ask your agent to “check my alicein queue” in a terminal. Your machine, your subscription, your timing.
Your agent finished it and handed it back. Open the card, read what it did and the comment thread, then check it off if you are satisfied. You close it; the agent does not.
It is a first draft from what you described and what is in your code. Drag, rename, and delete until it is your plan.
Yes — your agent does it, no integration required. See Bringing in existing work.
Beta maps do not yet redraw themselves as a repository drifts. If your code has changed shape substantially, ask your agent to update the map.
Not necessarily. The knowledge view says that no recorded correction means nobody has written one down. If a record matters and looks old, check it against what you can see.
That is the first-run walkthrough. Dismiss it and it stays dismissed.
You are probably in full screen, where the browser takes Esc for itself. Use ` or q instead. See Keyboard shortcuts.
They should not: every surface counts the same list. If you catch one that disagrees, tell us.

Still stuck

Email efidler@alicein.xyz.