work / lorx

Lorx

A git-compatible code forge in Rust, with change requests, its own actions engine, an automatic review engine and the bit CLI.

Open lorx.space How it works Lorx forge serverLorx actions engine and runner fleet
Years
2026
Status
active
Live
lorx.space

What it is

Lorx is a code forge that runs as one lorx serve process on SQLite or Postgres. Repositories are plain git over smart HTTP and SSH. bit is a superset of git with device-flow login, tokens kept in the system keychain, change requests and GitHub import.

Read more

It has its own workflow engine. A push is planned against .lorx/actions/ci.yml by the paths it touched, runs at the same head are deduplicated, and a runner pool wakes machines only when jobs are queued.

The review engine reads a change request's diff, the touched files, the repo's review rules and earlier threads, then writes inline comments tagged with one of five severities, info to critical, and reports a check that branch protection can require. On a self-hosted forge you bring the model: Anthropic, OpenAI or a local one.

Stack

  • Rust
  • SeaORM
  • SQLite
  • Postgres
  • gix
  • OpenAPI
  • Next.js
  • Expo
  • GCP
  • Anthropic
  • OpenAI

Counted

  • 350commits
    git rev-list, 2026-09-22 → 10-07
  • 90,420Rust lines
    line count across 8 crates
  • 399Rust tests
    #[test] and #[tokio::test]
  • 92OpenAPI paths
    openapi.json
  • 6bit release targets
    cargo-zigbuild / cargo-xwin

How it works

The system as a machine on a bench. Hover or use the arrow keys to drive it.

$ bit cr pushhead a41c9e2→ change #212main
The change: a canister, and the comb teeth it latches (one per CI job)Gate lamps: CI checks, then reviewA finding at the blocking severity (high)Lorx's forge as a post office. Only the CI jobs a change's paths call for run, and never twice for the same head; the two runner machines (two jobs each) start once a job has waited 20 s and stop after 15 idle minutes; the gate opens onto main only when every job passed and the review found nothing at the blocking severity.

The path through it

  1. git or bitPush over smart HTTP or SSH; bit adds device-flow login and change requests.
  2. lorx-serverGit hosting, the REST API in openapi.json, auth, change requests and auto-merge.
  3. lorx-actionsPlans workflows from .lorx/actions/ci.yml by the paths a push touched, and skips a run already done at the same head.
  4. Runner poolThe scheduler wakes machines when jobs queue; lorx-runner executes and reports each run as a check.
  5. lorx-reviewDiff, touched files, review rules and prior threads go to the model; inline comments come back with a severity, plus a check.
  6. MergeBranch protection can require the review check and the runs before a change lands.