Open source, free forever.

Own your project, not just your code.

Gitomi keeps issues, pull requests, project boards, milestones, comments, pipeline run records, notifications, and access-control events inside your Git repository - so you can work offline, sync with any Git remote, or self-host without losing your collaboration history.

cd cli && zig build

Start locally See how it works

No central database. No required server. No custom transport.

refs/gitomi/* signed project history

gitomi.localhost:12655/projects

Todo

#9f2a1c4 Document the signed event format issue.opened by alice/laptop

#37b40e1 Import GitHub labels into local index labels and milestone projected

Review

#a81f2d0 Render pull request file comments review note stored as comment.added

RUN pipeline: release.yml action.run_completed accepted

Done

ACL Team role grant projects correctly index rebuilt from inbox refs

alice@repo

$ gt issue open --title "Write release notes"
wrote signed issue.opened event
index rebuilt from refs/gitomi/inbox/*

Repository-owned collaboration

All project metadata lives in the same Git repo.

Issues, pull requests, comments, milestones, project boards, notifications, access-control changes, and pipeline run records are stored as Git-backed project history. Your repo becomes the source of truth for both code and collaboration.

Your repository refs/gitomi/*

maincode branchesnormal Git

v1.0tagsnormal Git

refs/gitomi/genesistrust anchorsigned manifest

inbox/alice/laptopissues, pulls, projectsevent commits

staging/origin/inboxfetched remote eventsvalidated before admit

runs/local-runnerpipeline diagnosticsretention-managed

issue.opened Write the release notes alice/laptop signed 9f2a1c4

issue.status_set Move issue to Review board rebuilt from accepted events

action.run_completed Pipeline result recorded diagnostics ref linked when present

IssuesPull requestsCommentsMilestonesProject boardsPipeline runsNotifications

Ordinary Git transport

Use any Git host, or host it yourself.

Gitomi syncs through ordinary Git. Use an existing Git service, a private remote, a mirror, or a fully local setup. If Git can fetch and push, your project workflow can move with it.

git transport

$ gt github import
imported 42 issues, 7 pull requests, 118 comments
$ gt sync
synced signed Gitomi refs through origin
rebuilt issues, PRs, projects, and pipeline status

refs/gitomi/genesis refs/gitomi/inbox/<principal>/<device> refs/gitomi/inbox/import-bot/github

Local clone create signed events

Any Git remote fetch / push refs

Mirror or bundle portable history

Self-host no required server

fetch validate project push

Local-first work

Work offline. Sync later.

Open issues, comment on pull requests, move project cards, inspect pipeline results already in your clone, and keep working locally. Reconnect when you are ready. Gitomi syncs project state through Git.

offline laptop 3 events queued

#c09b2aaOpen issuesigned
#a81f2d0Add PR commentlocal
RUNRead pipeline resultcached

team catches up accepted

deterministic projection rebuilt from accepted refs

Local CI/CD ownership

Own your CI/CD workflows locally.

Import your existing GitHub Actions workflows or define new ones, then run them on infrastructure you control. Gitomi gives you the flexibility to use your local setup and plug AI coding agents into CI/CD, while keeping workflow history and traceability in the repository.

resolve-conflict.yml workflow runs locally

Resolve merge conflict .github/workflows/resolve-conflict.yml

#142

1Checkout
2Local coding agent
3Publish

local coding agent

Mythos Coding Agent

Resolved conflict (+3 -5)

src/auth/session.ts (+3 -5)

-<<<<<<< HEAD

-return cachedSession ?? await refresh();

-=======

+return await loadSession({ cache: true });

->>>>>>> origin/main

Ran merge checks and unit tests

resolve merge conflict

Familiar model, different ownership

Keep the workflow close to the repo.

Use the familiar model: issues, pull requests, comments, labels, milestones, boards, pipeline runs, notifications, access control, and a local web UI. The difference is that your team owns the data and the history.

gitomi.localhost:12655/pulls/24

←

resolve merge conflict before release #24

Open maya wants to merge 1 commit into main from fix/release-conflict

Conversation 0 Commits 1 Files changed 2 +8 -3

maya opened today

Summary

Resolved the release conflict.
Kept both accepted changes and cleaned up the file.

ari Looks good. Thanks for resolving this.

👍 2

Workflow and checks local runner

checkout agent resolution publish result

buildpassed
testspassed
conflict checkpassed

Ready to merge

All checks passed.

Start locally

Bring Gitomi into an existing repository.

Initialize Gitomi, import existing GitHub project state, and open the local web UI. No central database is required for the project record.

Step 1

Import

Initialize Gitomi and import existing GitHub project state.

Initialize

gt init

Import from GitHub

gt github import

Step 2

Browse

Open the local web UI.

Open web UI

gt web

Reference

Reference documentation.

Read the product, ref layout, workflow, merge, and CLI documentation directly in the GitHub repository.

README CLI reference Product spec Ref spec Workflow spec Merge semantics