kenn-forge gives maintainers one local console for repository activity, pull requests, issues, reviews, and working sessions. It syncs provider data into SQLite and serves the UI from a single binary.
Linux, macOS, and Windows
Use kenn-forge to answer four daily questions:
- What changed across the repositories I maintain?
- Which pull requests and issues need attention?
- What can I review, update, or merge now?
- Which branch or task should I open locally?
New users should follow the Quick start. It covers installation, provider setup, repository selection, the first sync, and workspace creation.
Returning users can jump to a task:
- Follow activity across repositories
- Triage an issue
- Review a pull request
- Browse repository source
- Work in local sessions
- Read and edit local Docs
- Run daily maintainer workflows
- Connect Roborev, Kata, or Docs
- Change repositories, tokens, or modes
- Fix startup, authentication, or sync problems
Activity collects recent comments, reviews, commits, and state changes. Use threaded or flat mode, filter the queue, and open item details without losing your place.
Pulls and Issues combine lists, details, discussion, provider actions, and workspace creation. Unsupported provider actions remain visible but unavailable.
Workspaces opens durable local shells and configured agents against repository worktrees. Repos browses branches, tags, files, previews, and file history. Reviews connects to a running Roborev daemon. Docs reads, edits, pulls, and publishes registered Markdown folders. Kata issues appear where they are linked to a pull request, provider issue, or workspace rather than in a separate mode.
kenn-forge runs on your machine. Your provider, Kata daemons, and local files remain the source of truth.