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.
Connect from your project’s folder rather than your home directory, and make sure Claude Code is installed and signed in first.
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 its comment thread, then check it off if you are satisfied. Delivered is not done; you close it.
Expected. It is a first draft read out of what you described and what is in your code — roughly right, specifically wrong. Drag, rename and delete until it is your real plan.
Yes — your agent does it, no integration required. See Bringing in existing work.
Maps do not yet redraw themselves as a repository drifts. If your code has changed shape substantially, the map needs rebuilding.
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 does, that is a bug worth telling us about immediately, because it is exactly the failure we designed against.

​
Still stuck

Get in touch and we will sort it.