Repo-Native PM · building per SPEC

The repo is the project tracker.

Issues live in git as the single source of truth. Agents write them via JSON CLI. You move them on a Kanban board. ProGit commits the changes and syncs them to every developer's machine. No webapp database. No GitHub Issues. Just your repository.

Agent writes
prog issue create --json --actor agent:voxis
Human moves
drag the card to "In Progress"
Sync commits
prog sync → one commit, pushed to origin
Every clone sees it
git pull → board updates → agent re-adjusts
repo-native sync — stage and flush
machine A — developer
$ prog issue create --title "Fix auth race" --actor agent:voxis --json
✓ created abc123 → .project/issues/abc123.json
$ prog board # you move abc123 to "In Progress"
$ prog sync # flush: stage → commit → push
✓ committed 1 issue change to .project/
✓ pushed to origin
 
machine B — another developer
$ git pull && prog board
✓ abc123 now shows "In Progress"
$ git log --oneline -- .project/
a1b2c3d progit: sync 1 issue change — abc123: backlog → in-progress (agent:voxis)

The repo replaces the webapp database.

Not "issues in your terminal." Not "a faster Jira." The repository itself is the project management system — storage, history, sync, audit, all of it. Git is the transport.

Repo is the database

Issues live in .project/issues/*.json, tracked in git. The single source of truth is the commit graph — git log is your project history. No webapp owns your tickets.

Agent ledger CLI

prog issue create|set|note --json --actor agent:name. Stable envelope, stable exit codes. Machines write issues without a TUI; you audit what they did.

Board is a working tree

Move cards on the Kanban board. Changes stage locally, like editing files. Nothing commits until you say so — no per-drag commit spam.

Sync is a commit + push

prog sync flushes every pending change as one git commit and pushes to origin. Every clone pulls the new board state. That's the whole transport.

Forge federation bridge

Git-native is the spine. Forgejo and GitLab REST sync ride alongside as a peer transport — migrate off GitHub Issues without ripping the bridge.

Sober hard-floor

Plugins reach host actions only through explicit allowlists. No arbitrary CLI pass-through. Signed releases, minisign, checksums.

Offline Ollama review

Diff review on your laptop. The role stays in the primary prompt path; nothing silent, nothing auto-applied without you.

Plugin marketplace

LuaJIT plugins, declared capabilities, native prog plugin dispatch, async job scheduler, Dilithium-signed registry path.

Get ProGit v0.10.0-beta

Signed binary on Forgejo · AUR package live · released July 21, 2026. Prefer package managers; build from source when you want the bleeding edge.

AUR (Arch)

prebuilt 0.10.0_beta-1

yay -S progit-bin

Signed binary

v0.10.0-beta · ~6.9MB

Download the linux x86_64 tarball from the Forgejo release, verify SHA256 + minisign, install prog.

One-line installer

PROGIT_VERSION=0.10.0-beta optional pin

scripts/install.sh from the sovereign Forgejo — detects arch, verifies signature, installs to ~/.local/bin.

From source

default features stay under 7MB

git clone · cargo build --release · link target/release/prog
A
Arch Linux (AUR)
yay -S progit-bin
# or: paru -S progit-bin
prog --version
B
Signed linux x86_64 binary
# download + verify from
# https://git.sovereign-society.org/ProGit/progit/releases/tag/v0.10.0-beta
# artifact: prog-0.10.0-beta-x86_64-unknown-linux-gnu.tar.gz
tar -xzf prog-0.10.0-beta-x86_64-unknown-linux-gnu.tar.gz
install -m755 prog ~/.local/bin/prog

Direct tarball →  ·  All assets + signatures →

C
Sovereign installer script
# fetch install.sh from sovereign Forgejo (main), then run with sh
# https://git.sovereign-society.org/ProGit/progit/raw/branch/main/scripts/install.sh
PROGIT_VERSION=0.10.0-beta sh install.sh
D
Build from source
git clone https://git.sovereign-society.org/ProGit/progit
cd progit
cargo build --release
# prefer ~/.local/bin or ~/bin — avoid stale /usr/local/bin shadows
install -m755 target/release/prog ~/.local/bin/prog
cd your-project && prog init && prog

Full installation guide →   •   AUR package →   •   Browse source →

Looking for Dogfooders

Project management that lives in your repo.

ProGit is pivoting from a terminal issue tracker to a repo-native project management system. Agents write issues via JSON CLI. You move them on a Kanban board. Sync commits the changes and pushes them to every clone. No webapp database between your team and your project state — just git.

What we need

  • Teams running coding agents on real projects
  • Edge cases from multi-developer board sync
  • Migration stories off GitHub/GitLab Issues
  • Feedback on the stage-and-flush model

What you get

  • Project management with no webapp dependency
  • Full git history of every ticket change
  • A board your agents can read and write
  • Direct influence on the roadmap

Acknowledgments

ProGit is developed as an open-source project by independent consultants. We extend our sincere gratitude to Dlabs Kft for generously providing real-world infrastructure resources and allowing us to battle-test ProGit while building the Mosaic Blockchain ecosystem and the Mosaic Trust Network.

Their trust enables us to develop production-hardened tooling that benefits the entire community.

Built with purpose. Tested in production. Open for all.