Repository wiki
iKAgent → Wiki has one card for each repository connected to iKanban: the workspace’s iKanban GitHub App repositories, the GitHub repositories linked to projects of your teams, and the repositories linked to your own GitHub connection. An agent reads the repository and writes its wiki into Documents, in a folder named after the repository, inside Wiki of the team you pick. Wiki pages are ordinary documents: you can search them, share them, and see older versions in each page’s history.
Generate a wiki
- Open iKAgent → Wiki.
- On a repository’s card, select Generate (or Regenerate).
- Pick who writes it: Claude, Copilot or Gemini, on my machine.
- Pick what to cover: Overview, Architecture, Setup and running, API and modules.
- For a repository with no wiki yet, pick the team. The wiki folder goes in that team’s Documents.
- Select Generate. A session starts on your laptop runner and its page opens.
The agent writes one page per section, then records the commit it read. It does not change the repository’s files, commit or push.
The card
- No wiki yet, Up to date, or N commits behind: how far the default branch moved since the wiki was written.
- Generated with a time: iKanban could not ask GitHub this time, so the freshness is not known.
- Open in Documents opens the wiki folder.
- Regenerate after N commits sets when the wiki regenerates on its own. Only workspace owners and admins change it, then select Save. Members see Only workspace owners and admins can change this.
- Auto-regenerate skipped: with a reason and a time, when the last automatic check skipped this wiki. The line goes away after a check that does not skip.
Automatic regeneration
When a repository is N or more commits ahead of the wiki, iKanban regenerates the wiki on its own. N is set on each card, and is 5 by default for a new repository. A card made before keeps its N.
The automatic run acts as the person who last generated the wiki. It uses their runner, their GitHub sign-in and the agent they picked last, and it writes all four sections. Its session is a task in the wiki’s team: the team’s first project by name, and its feature AI agents (else its first feature). The workspace AI policy is checked on that task, as for every automatic agent run.
The rules that decide whether a wiki regenerates
These are deliberate. A skipped run shows its reason on the card: Auto-regenerate skipped: …. Each row says what to change.
| Rule | What happens | Where you see it | Change it |
|---|---|---|---|
| Checked every 10 minutes | iKanban compares each generated wiki with its repository every 10 minutes. A wiki can start up to 10 minutes after it falls N commits behind. | the card’s badge | — |
| N commits, default 5 | The wiki regenerates when the default branch has N or more new commits since the wiki’s commit. N is a whole number above 0, per repository. Only workspace owners and admins change it. | Regenerate after N commits on the card | a workspace owner or admin, on the card; then Save |
| One hour between automatic starts | An automatic run starts at most once an hour per wiki, also when the last run failed. | the card stays N commits behind | wait, or select Regenerate |
| One run at a time | No automatic run starts while a run of the same wiki is still queued or running. | the session in progress | wait for it to end |
| The last generator’s runner is offline | Skipped. | Auto-regenerate skipped: the generator’s runner is offline | that person opens the iKanban app |
| No GitHub connection, or the repository is not connected | Skipped, when the last generator has no GitHub connection, or the repository is no longer in the workspace’s GitHub App, a project of their teams, or their linked repositories. | Auto-regenerate skipped: the generator has no GitHub connection (or the generator can no longer see the repo) | that person connects GitHub in Agent settings → Connections, and the repository is added back to the GitHub App, a project, or their linked repositories |
| GitHub gave no answer | Skipped for this check, when GitHub’s compare does not answer. | Auto-regenerate skipped: GitHub’s compare gave no answer | — the next check tries again |
| The last generator left the team | Skipped, when that person is no longer in the wiki’s team. | Auto-regenerate skipped: the generator is no longer in the wiki’s team | someone in the team selects Regenerate; they become the generator |
| The wiki’s team has no project | Skipped: the session task needs a project in the wiki’s team. | Auto-regenerate skipped: the wiki’s team has no project | add a project to the team |
| Workspace AI policy | Skipped, when the workspace or team policy turns AI, or the agent, off. | Auto-regenerate skipped: with the policy’s reason | a workspace admin, in Agent settings → Workspace AI controls |
| Active subscription | Wiki pages are documents, and creating or editing a document needs an active subscription (active, trial or past due) on the workspace. Without one, the wiki run cannot write its pages. | in the app, the dialog Subscription inactive: This workspace’s subscription is inactive. Reactivate to continue creating and editing.; in a wiki session, the agent reports a 402 subscription_inactive | Settings → Billing (the dialog’s Reactivate subscription) |
| Read-only workspace | Skipped. A disabled workspace is read-only, so nothing is written. Saving N is refused too. | Workspace disabled — read-only mode | contact iKanban support |
| Never generated | A repository with No wiki yet never regenerates on its own. | No wiki yet | select Generate once |
| Laptop runner only | Generate offers only my machine. A GitHub run has no iKanban key to write Documents with. | the three choices in Who writes it | — |
| Where the session lives | Generate by hand starts a session task in team IKA, project ai-agent, feature AI agents, like every session you start. An automatic run’s session is a task in the wiki’s own team. | the session list | a workspace admin adds you to team IKA |
| Your team’s wikis only | You see and change a wiki only when you are in its team. | This repo’s wiki belongs to a team you are not in | join that team |
| Freshness check: 25 wikis, 5 minutes | One page load asks GitHub about at most 25 wikis, and keeps each answer for 5 minutes. Other cards show Generated with a time. | the card’s badge | reload in a few minutes |
| Calls to iKanban are allowed in wiki runs | Under Ask me, Allow pull requests and Deny, a wiki run may still call iKanban’s API without asking, for the folder, document and wiki calls it needs. Every other push or network call follows your choice. This applies to Claude and Copilot. | the session runs without Needs approval for those calls | Agent settings → Runners → Risky actions |
| Gemini’s own approvals | Gemini runs through Antigravity and follows its own approval rules. If it asks, allow the calls to iKanban. | the note under Who writes it | Antigravity’s own rules |