Documentation · Quick Start · Configuration
A local maintainer console for pull requests, issues, reviews, activity, and workspaces.
kenn-forge 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.
Activity keeps the selected pull request beside its live workspace and coding-agent session.
- 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.
Provider capabilities vary. kenn-forge shows unsupported actions as unavailable.
Download the archive for your system from
GitHub Releases. Releases
include a SHA256SUMS file.
| System | Architecture | Archive |
|---|---|---|
| Linux | x86-64 | forge_<version>_linux_amd64.tar.gz |
| Linux | ARM64 | forge_<version>_linux_arm64.tar.gz |
| macOS | Intel | forge_<version>_darwin_amd64.tar.gz |
| macOS | Apple silicon | forge_<version>_darwin_arm64.tar.gz |
| Windows | x86-64 | forge_<version>_windows_amd64.zip |
| Windows | ARM64 | forge_<version>_windows_arm64.zip |
| Android | Universal | forge_<version>_android.apk |
On Linux, macOS, and Windows, extract the archive and move kenn-forge or
kenn-forge.exe to a directory on your PATH.
The Android APK installs a client app for phones and tablets that connects to a Forge server you already run. Install the APK, open the app, and enter the server's full URL and its auth token if the server requires one.
Build the current source when no release is published:
git clone https://github.com/kenn-io/forge.git kenn-forge
cd kenn-forge
make installSource builds require Go 1.27.4+ and Bun.
GitHub users can reuse an authenticated GitHub CLI session:
gh auth login
kenn-forge daemon startOpen 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.
For Docker or Umbrel, use the local image and startup settings.
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.
A gh symlink to kenn-forge (or kenn-forge gh ...) is an opt-in stand-in
for gh that answers piped gh pr list and gh pr view <number> JSON queries
from synced Forge data and passes everything else to the real gh. See the GitHub CLI shim guide for
setup, supported queries, and debug logging.
- Quick Start
- Workflows
- Integrations
- Configuration
- Commands
- MCP companion
- GitHub CLI shim
- Troubleshooting
kenn-forge is licensed under the MIT License. Copyright (c) 2026 Kenn Software, Inc.. See NOTICE for earlier contributor attribution.