open-loops 1.3.0

Recupere o contexto de trabalhos pausados: o que começou, onde parou, qual o próximo passo
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130

# open-loops

[![CI](https://github.com/carvalhosauro/open-loops/actions/workflows/ci.yml/badge.svg)](https://github.com/carvalhosauro/open-loops/actions/workflows/ci.yml)
[![crates.io](https://img.shields.io/crates/v/open-loops.svg)](https://crates.io/crates/open-loops)
[![MSRV](https://img.shields.io/badge/MSRV-1.89-blue)](rust-toolchain.toml)
[![license](https://img.shields.io/crates/l/open-loops.svg)](LICENSE)

> What did I start and not finish? Where did I leave off? What's the next step?

`loops` lists your paused work (unmerged branches across all your repos) and
reconstructs resume context from your AI sessions and git — without you
documenting anything.

All user-facing output is in English: CLI messages, errors, resume sections,
and docs.

## Install

```bash
# via cargo
cargo install open-loops

# via script (Linux/macOS)
curl -fsSL https://github.com/carvalhosauro/open-loops/releases/latest/download/open-loops-installer.sh | sh

# via Homebrew (requires carvalhosauro/homebrew-tap — see docs/distribution.md)
brew install carvalhosauro/tap/open-loops
```

## Quickstart

```bash
# 1. register where your repos live
loops init ~/repo

# 2. inventory — open loops, most idle first (<5s, no LLM)
loops
# scanning git repositories…
# LOOP                    IDLE FOR  AHEAD  BEHIND
# my-app/feat/login            12d      3       1
# api/fix/timeout                 2d      1       0

# 3. audit evidence before distilling (no LLM call)
loops resume feat/login --dry-run
# scanning git…
# matching AI sessions…
#
# # my-app/feat/login
#
# **Confidence:** medium — AI sessions found but alignment uncertain — audit Sources before trusting
#
# ## Git
# ...
# ## AI sessions
# - abc123.jsonl (modified 2026-06-18) [in commit window, mentions branch]
#
# ---
# Dry run — LLM not invoked. Run without `--dry-run` to distill.

# 4. resume: why, done, remaining, next step + auditable sources
loops resume feat/login
# scanning git…
# matching AI sessions…
# distilling…
#
# # my-app/feat/login
#
# **Confidence:** medium — AI sessions found but alignment uncertain — audit Sources before trusting
#
# ## Why
# Adding OAuth login to unblock the onboarding flow.
#
# ## Done
# - Token validation middleware
# - Login form wired to `/auth/login`
#
# ## Remaining
# - Refresh token rotation
# - Error states on the form
#
# ## Next step
# Implement refresh token rotation in `auth/refresh.rs` and add a test for expiry.
#
# ## Sources
# - git: branch feat/login (HEAD a1b2c3d)
# - AI session: abc123.jsonl (modified 2026-06-18)
```

Progress lines go to **stderr** so you can pipe or redirect stdout without
losing the distilled document. Long steps (`distilling…`) can take ~30–60s on
a cold run; repeat calls are instant from cache.

State lives in `~/.open-loops/` — nothing is written inside your repos.

## Audit before you trust

Every resume ships a **confidence score** and a **`## Sources`** section — not
metadata for debugging, but the audit trail you use to decide whether to trust
the distillation.

| Score | Meaning | What to do |
|---|---|---|
| `high` | AI sessions overlap branch commits and mention the branch name | Usually safe to continue |
| `medium` | Sessions matched heuristically | Read **Sources**; confirm sessions match this branch |
| `low` | No AI sessions matched — context from git only | Treat as a draft; verify **Sources** and diff yourself |

Recommended flow when confidence is not `high`:

1. `loops resume <branch> --dry-run` — inspect matched commits and sessions (no LLM).
2. Check **`## Sources`** in the full output — do those commits and sessions belong to this work?
3. Run `loops resume <branch>` only when the evidence looks right.

## Demo

Record or replay locally:

```bash
cargo build --release
./scripts/demo.sh          # runs the quickstart flow in a temp dir
asciinema play docs/demo.cast   # replay the bundled recording
```

## Docs

Full reference in [`docs/`](docs/): [setup](docs/setup.md) ·
[features](docs/features.md) · [configuration](docs/configuration.md).

## License

MIT OR Apache-2.0.