Troubleshooting

The failures people actually hit with Laimonade — empty Ready menus, stale menu numbers, items that will not submit, silent agents — and what each one means.

Last reviewed · maintained by Founder

How to read this page

Each heading is the symptom as you would describe it. Most of what follows is not a bug but a boundary behaving as designed, which is worth knowing before you spend an afternoon on it.

My agent says the Ready list is empty

An empty menu is a real answer, not a failure. It means nothing is in the Ready column of this week's sprint.

Open the Board and check. Work sitting in Backlog is invisible to an agent by design — Ready is the contract that says "this is specified well enough to act on". Move an item into Ready, or ask Laimon to add it to the sprint, and ask again.

My agent says a number is not valid

Menu numbers are session state. They refer to the most recent list the agent asked for, so a number from an earlier menu — or from a different filtered menu — will not resolve.

Ask for the menu again and use the fresh numbers. If your agent is holding a number from several turns ago, telling it to re-list is faster than arguing about which list it meant.

It refuses to submit an item for review

Only an item sitting Ready on the current sprint can be submitted. Two common causes:

  • The item is still on the backlog. Add it to the sprint first.
  • The item is already In Review. Submitting again is a no-op, and the refusal is telling you the work is already waiting for a person.

I am asked to sign in again

Access follows your project membership. If you were removed from the project, or the connection was revoked, your agent will ask you to reconnect and will not be able to until access is restored.

Signing in again is also the fix after a project API key is regenerated: the old key stops working everywhere it was configured, immediately and by design.

My agent connected but sees the wrong project

A connection can be granted more than one project. When it is, every call names its target, and every reply is stamped with the project that answered — so check the stamp on the reply before assuming the wrong backlog was read.

Ask your agent to call list_projects to see the granted set, and change it from the MCP page in the app. No reconnect is needed.

Commits are not appearing on my items

Three things have to be true, in order: GitHub is connected, the repository is tracked, and the commit is matchable to an item.

Matching is confidence-based and deliberately conservative. A match at 80% or better moves the item to In Review and records the commit; 70–79% is recorded as a pending match for you to accept or reject; below 70% nothing is recorded at all, because attaching a commit to the nearest plausible item is worse than leaving it unattached.

If a commit should have matched and did not, the usual cause is a message that describes the change rather than the work — "fix validation" against forty open items is not enough to go on. Reference the item, or accept the pending match when it is offered.

Laimon told me it did something, and it did not happen

Report it. This class of failure is taken seriously here: Laimonade runs a verifier over its own replies specifically to catch claims that do not match what its tools actually did, and several such bugs have been found and fixed that way.

What helps most in a report: the project, roughly when it happened, and what Laimon said it had done. That is enough to find the trace.

My roadmap progress looks wrong

Progress is computed from completion dates, not from statuses, because the weekly rollover overwrites statuses when it archives finished work. An item finished before completion dates were recorded reliably can therefore look unfinished on the roadmap while reading as done everywhere else.

If a milestone's figure looks wrong on recent work, tell us — that is a bug rather than a setting.

An agent changed something I did not expect

Everything an agent can do is listed in the MCP tool reference, with its permission. Three tools are marked destructive, and your MCP client should be asking you before it runs those.

What no agent can do: mark work Done, or reach another project. If you believe one of those happened, that is a security issue and we want to hear about it immediately.

Still stuck

Email support@laimonade.com. For anything that looks like a security issue, say so in the subject line and we will treat it as such.

If a page in these docs describes behaviour the product does not have, that is worth reporting too — documentation that is trusted and wrong is worse than documentation that is missing.