kenn-forge
kenn-forge is a local maintainer console for pull requests, issues, reviews, activity, and local workspaces. It syncs the repositories you maintain into a local SQLite database and serves the UI from one binary.
Start with the user guide for setup and workflows.
Teaser
Activity keeps the selected pull request beside its live workspace and coding-agent session.
What you can do
- Triage activity across repositories and provider hosts.
- Review pull requests and merge requests with discussion, diffs, and CI context.
- Work with issues without leaving the console.
- Create local workspaces for hands-on review or implementation.
- Read and respond to Roborev reviews from a running daemon.
- Link Kata issues to provider work and local workspaces.
- Browse and edit registered Markdown folders.
- Expose cached maintainer workflows to local MCP clients from the daemon.
- View and operate remote kenn-forge daemons through a federated fleet.
Install a release
Download the archive for your system from
GitHub Releases. Releases
include a SHA256SUMS file.
| System | Architecture | Archive |
| --- | --- | --- |
| Linux | x86-64 | forge_ |
| Linux | ARM64 | forge_ |
| macOS | Intel | forge_ |
| macOS | Apple silicon | forge_ |
| Windows | x86-64 | forge_ |
Extract the archive and move kenn-forge or kenn-forge.exe to a directory on
your PATH.
Build the current source when no release is published:
git clone https://github.com/kenn-io/forge.git kenn-forge
cd kenn-forge
make install
Source builds require Go 1.27+ and Bun.
Start
GitHub users can reuse an authenticated GitHub CLI session:
gh auth login
kenn-forge daemon start
Open http://127.0.0.1:8091. First-run setup connects a code forge, adds
repositories, runs the first sync, and opens a pull request.
Use kenn-forge serve when you want the server attached to the foreground for
development or diagnosis.
The Repositories panel selects provider hosts and repository patterns. GitLab,
Forgejo, and Gitea hosts reuse an authenticated glab or fj session the same
way. Configure explicit credentials through environment variables or
~/.kenn/forge/config.toml; see Configuration.
Local workspaces require Git and tmux on a Unix-like host. The Windows release supports the dashboard and provider actions. Use WSL or a remote Unix-like kenn-forge host when you need workspace sessions.