Spaces:
Running
Running
File size: 1,640 Bytes
26a284a | 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 | # commit-context worked examples
## 1. Line range with a linked session
User: "Why is this retry loop here?" (pointing at lines 40-52 of refresh.ts)
Find the SHA:
```bash
git blame -L 40,52 src/auth/refresh.ts
# 9a1b2c3d (dev 2026-06-07) ... retry on revoked token
```
Look it up:
```json
memory_commit_lookup { "sha": "9a1b2c3d4e5f60718293a4b5c6d7e8f901234567" }
```
Response:
```json
{
"commit": { "sha": "9a1b2c3d...", "short": "9a1b2c3", "branch": "main",
"author": "dev", "message": "rotate refresh tokens" },
"sessions": [ { "id": "7f3a9c21", "project": "app", "observationCount": 14,
"summary": "Reworked refresh rotation" } ]
}
```
Present:
> `9a1b2c3` on `main` by dev: "rotate refresh tokens". Linked to session
> `7f3a9c2` "Auth refresh rework" (14 obs). The retry loop handles a token
> revoked mid-flight, per the session's high-importance observations.
## 2. Function lookup, commit predates linking
User: "What was the agent doing when it wrote validateScope?"
```bash
git log -L :validateScope:src/auth/scope.ts -n 1
# 1122aabb ...
```
```json
memory_commit_lookup { "sha": "1122aabbccddeeff00112233445566778899aabb" }
```
Response:
```json
{ "commit": null }
```
Present:
> `1122aab` predates agent session linking, so there is no recorded session.
> From `git show`: it added `validateScope` to enforce per-token scopes. I can
> show the full diff if useful.
## 3. Bare path
User: "Give me context on src/middleware/limit.ts."
```bash
git log -n 1 -- src/middleware/limit.ts
```
Take the SHA, run `memory_commit_lookup`, present commit plus linked session in
the same shape as example 1.
|