Gitorii
Source

Roadmap

What is being built

Shipped means it is on crates.io. In progress means the work has started and there is code behind it. Considered means the direction is real and the date is not.

shipped: 0.13.0

in progress

  • A graphical application

    A window for the people who want one, over the same domain layer the CLI and the TUI already share — so it inherits the snapshots, the scanner and the platform clients rather than reimplementing them. It is the one row on the comparison page where Gitorii currently says "on the roadmap" instead of yes.

  • torii remote visibility, everywhere

    Flipping a repository between public and private works on GitHub and GitLab. The same call exists on Gitea, Codeberg, Forgejo and Bitbucket and is not wired yet; Azure puts visibility on the project rather than the repository, and Radicle has no central notion of it at all.

  • A static binary as a release artifact

    The `static` feature on the musl target already produces a binary with no runtime libraries. What is missing is the CI job that builds it on every tag, so it is a thing you download rather than a thing you compile.

next

  • torii ci configure

    Guided setup of each platform’s CI from one command, instead of copying a .gitlab-ci.yml or a workflow file from the last project.

  • Interactive staging

    `torii save --patch`, to stage hunks rather than files. The TUI stages by file today; this is the CLI half.

  • Scanner: fix, not just find

    `scan --fix` to strip a detected secret from the staged content, a pre-push pass as well as pre-save, and an organisation-wide pattern file shared across repositories.

  • Runner visibility

    A flat list of every runner across your platforms — idle or busy, version, last seen — and the ability to kill one that has wedged the queue. Not provisioning: the platforms already have tools for that.

considered

  • Snapshot improvements

    Compression for old entries, a diff between two snapshots, and opt-in backup to a private bucket. Also the known bug: `snapshot stash` occasionally reports success without saving.

  • AI-assisted commit messages

    A message drafted from the staged diff, and a conventional-commit validator. Drafted, never committed for you.

  • A version control system of its own

    The long horizon. torii is a Git client; the goal is a system designed around how people work rather than around Git’s data model, with torii as the migration path off Git when there is somewhere to migrate to.

  • Not planned: a repository browser on gitorii.com

    Hosting and browsing repositories is what GitHub, GitLab and Codeberg do. This site stays documentation and a logbook.

Nothing here carries a date. A date on a roadmap maintained by one person is a promise made with someone else's time — the order is the commitment, not the calendar.