Ask about the code

Ask kanman where something is handled, why it is built this way, what changed last week or who knows a part of the code. Every answer links the files and lines, pull requests, decisions and stories it stands on.

kanman knows your team’s repositories, its stories, decisions and context. Ask it about the code in the team’s chat, like you would ask a colleague who has been around for a while.

What you can ask

Question Example What you get
Where is something handled? “Where is invoice VAT handled?” The most likely place, as file:line with a link to the line on your code host, and the other places that match
Why is it built this way? “Why was the export built this way?” The reasons kanman finds in decisions (also the ones taken in meetings), pull requests, commits and stories, each linked
What changed? “What changed last week?”, “What changed in the last 3 days?” The pull or merge requests merged in that time, the stories kanman delivered and the decisions recorded
Who knows it? “Who knows the billing code?” The people who changed the matching code or merged changes about it, each with the reason

You can ask in English, German, French or Spanish. Shorter windows (“What changed in the last hour?”) get kanman’s own activity instead.

Every answer comes with a card of links: places in the code, pull or merge requests, commits, decisions, stories, team context and people. kanman answers only from what it finds. When nothing matches, it says so and what would help, instead of guessing.

New in the team

An empty team chat starts with New here? Ask me about… and three questions. Where should I start?, How do the repositories fit together? and Who owns what? get one answer with:

  • the team’s repositories and the people who work on each most,
  • the team’s memory and skills: its decisions, conventions and procedures (see Memory and skills),
  • small stories that are a good start.

Where the answers come from

kanman starts from the team’s repository pages in Team › Memory and skills › Repos (see Memory and skills). Each page is as of a commit; the answer’s card lists the pages it used with that commit, and where a page and the code differ, the code wins. Pages nobody checked for two weeks are not used.

kanman reads the team’s repositories on your code host with the team’s connection: code search, the history of the matching files and the merged pull or merge requests. If your workspace runs everything on your own runners, your runner reads the code with its own access; only file names, line numbers, a short line of context and links come back, and the answer is written by a model on your runner (see Runner-only mode). If the runner is offline, kanman answers from its own records and says that the code was not read.

Team context is used only when the team has it switched on, with the same permissions as other answers (see Team context and connectors).

From Claude Code or Codex

The same questions work from your coding agent over the kanman MCP with the tool ask_kanman.

Last updated: January 1, 0001

Open kanman