Ask the Wiki What Was Decided

Recall answers from your wiki before you or your agent change something. Ask "why did we do it this way?" or "what is still open about the mobile SDK?" and your agent answers with each decision's owner, date, and the option it was chosen over, each open question with its owner, and the pages it read.

Run recall

In Claude Code, with the Nimbalyst Wiki plugin:

/nimbalyst-wiki:recall payment retries

Give it a question or an area. Without one, it covers the area of the work at hand. You can also just ask, and the agent uses recall on its own for questions like these:

• "Why did we put retries in the event queue?"
• "What did we decide about auth?"
• "Is there a decision on the mobile SDK?"
• "What is still open for the launch?"
• "What does the wiki say about deploys?"

In Codex, Cursor, VS Code, Cowork, and other agents, ask the same questions in your own words. They use the same wiki tools.

How it answers

1. Decisions and open questions first. The agent searches the decided and open marks across the wiki with two or three key words from your question. For "what did we decide" it looks at decisions, for "what is still open" at open questions, and when you name a person, at what that person decided or owns.
2. Then pages. It searches the wiki for the area. When the work is about to change code, it also finds the pages that cover those files and treats them as required reading.
3. Reads a few pages in full. About five at most. The reasoning behind a decision is in the sentences around it, so it reads the page, not only the mark.
4. Answers with sources. Each decision comes with who made it, when, and what it was chosen over; each open question with its owner. It names every page it used with its path in the wiki folder.
5. Flags what may be out of date. It says when a page is stale because the code it covers changed, or when a page has the status outdated, and it keeps what the wiki says apart from what it infers.

If the wiki has nothing on the question, the agent says so in one line and answers from the code or the conversation, labelled as such. If you then decide something, capture records it.

Recall only reads. It never changes a page.

Pages that cover code

A page can name the code it explains in a paths field, as a list of repository-relative globs in .gitignore style:

paths: [src/payments/**, "!src/payments/generated/**"]

The wiki matches those globs against changed files to find the pages a change affects. Recall uses it to find what to read before code changes, and capture uses it to update the pages a session's changes touched. See Local Wiki Files and Location for the page format.

In Claude Code, the plugin also tells the agent at the start of each session what your local wiki covers and which pages cover the files you have changed, so it starts from what the wiki already says.

Catch up yourself

Recall is for questions. To see everything at once, open the wiki in your browser and read the index of decisions and open questions, or place those lists on Home. See Read and Edit the Wiki in Your Browser and Lists of decisions and open questions.