status

Show the branch-aware status: local changes, then your branches and their commits. This is the default command, so git loom alone runs it.

Usage

git loom [status] [-f [<commit>...]] [-n <N>] [-a]

Options

Output

╭─ zz [local changes]
│   ma  M src/main.rs
│   nf A  new_file.rs
│   un  ⁕ untracked.txt
│
│╭─ fb [feature-b] ✓
│●    pop  d0472f9 Fix bug in feature B
│●    hug  7a067a9 Start feature B
├╯
│
│╭─ fa [feature-a] ↑
│●    dog  2ee61e1 Add feature A
├╯
│
● ff1b247 (upstream) [origin/main] Initial commit

From top to bottom:

1. Local changes (zz): conflicted files (!!), then changed files with their git status --short code, then untracked files (⁕). Shows no changes when the working tree is clean.
2. Loose commits: commits on the integration branch that belong to no feature branch.
3. Feature branches: empty ones first, then each branch with its commits, newest first.
4. Upstream: the commit your branches are based on.

Symbols

Short IDs

Every branch, commit and file gets a short ID — what you see is what you type in other commands. zz always means all local changes.

• Commits made by loom get a persistent ID of three or more letters, such as pop. It comes from the commit’s Change-Id trailer, so it survives every rewrite. IDs alternate a consonant from c d f g h m n p r s t w y and a vowel from a e i o u, so every ID can be said aloud and many are words (pop, sun, dog); the letters were picked to spell short words, with look-alikes left out. Other commits get a hash prefix, such as 3a, which changes when the commit is rewritten. In the rare case where an ID of four or more letters is also a prefix of some object’s hash, loom refuses the ambiguous argument instead of guessing; give the full hash or the Change-Id.
• IDs are as short as they can be while staying unique. When a new commit shares an ID’s first letters, both IDs grow, and the shorter form stops working rather than point at the wrong commit.
• Any longer prefix of a letter ID works too; a hash ID works from four characters, as in git.

Showing Files

git loom status -f dog

│╭─ fa [feature-a]
│●    dog  2ee61e1 Add feature A
│┊      dog:0 M  src/feature.rs
│┊      dog:1 A  tests/feature_test.rs
├╯

Commit files get IDs such as dog:0, which fold accepts to move or uncommit a single file.

Branch Layouts

│╭─ fb [feature-b]        │╭─ fv [feature-a-v2]     │╭─ fs [feature-stale]
│●    pop  4e046ab B      │├─ fa [feature-a]        ├╯
││                        │●    dog  2ee61e1 A      │
│├─ fa [feature-a]        ├╯
│●    dog  caa87a9 A
├╯

From left to right: feature-b stacked on feature-a; two branches sharing one tip; an empty branch at the base.

When upstream has moved on since your base:

│●  [origin/main] ⏫ 3 new commits
├╯ 204e309 (common base) 2025-07-06 Merge pull request #10

Hidden Branches

Branches starting with loom.hideBranchPattern (default local-) are hidden, commits included — handy for local-only configuration. Every other command still accepts them. --all shows them.

Agent Mode

With --agent, the tree goes to stderr and stdout gets the same graph as JSON, under graph:

{"status":"ok","graph":{
  "schema": 1,
  "integration_branch": "integration",
  "cwd_prefix": "",
  "local_changes": {"id": "zz", "files": [
    {"id":"ma","path":"src/main.rs","index":"M","worktree":" ","state":"tracked"}]},
  "branches": [
    {"names": [{"id":"fu","name":"feature-ui","remote":null}],
     "stacked_on": "feature-api", "stacked_on_hidden": false,
     "commits": [{"id":"sun","hash":"9c1d044","oid":"9c1d0448…",
                  "subject":"feat(ui): settings panel","change_id":"I9c1d…","files":[]}]}
  ],
  "loose_commits": [],
  "upstream": {"label":"origin/main","base_hash":"7f3e9b0","base_oid":"7f3e9b0c…",
               "base_subject":"chore(release): 2.4.0","base_date":"2026-09-14","commits_ahead":0},
  "context_commits": []
}}

Prerequisites

• On a branch with an upstream