Skip to content
Open
Show file tree
Hide file tree
Changes from 42 commits
Commits
Show all changes
49 commits
Select commit Hold shift + click to select a range
82a583e
feat(cli): /sessions search, /resume --limit, richer session listing …
Esashiero Jul 30, 2026
1d7a513
feat(cli): upgrade /sessions search to FTS5 content matching with ric…
Esashiero Jul 30, 2026
2e22d51
fix(cli): add Model+Msgs columns to hermes sessions list
Esashiero Jul 30, 2026
b22a0e6
feat(cli): add 'hermes sessions search <query>' CLI subcommand
Esashiero Jul 31, 2026
9826fcf
wip: add diagnostics to /sessions search for debugging
Esashiero Jul 31, 2026
badf310
fix(cli): _cprint() requires str arg — replace empty calls with _cpri…
Esashiero Jul 31, 2026
151afc2
fix(cli): /sessions search — show session IDs, dedup compression chil…
Esashiero Jul 31, 2026
52527c5
fix(cli): revert /sessions search to table format, add ID col + compr…
Esashiero Jul 31, 2026
a23d394
fix(cli): /sessions search — show all 10 matches, better preview, add…
Esashiero Jul 31, 2026
6e7e9a6
fix(cli): /sessions search — batch-fetch previews from messages table
Esashiero Jul 31, 2026
d34697b
fix(cli): /sessions search — add back compression child dedup
Esashiero Jul 31, 2026
2d1486e
fix(cli): /sessions search — sort by recency, root-ancestor previews,…
Esashiero Jul 31, 2026
e02c6bb
fix(cli): /sessions search — Model + token counts + preview back inline
Esashiero Jul 31, 2026
0b4260b
fix(cli): /sessions search — title column = longest result title, cap…
Esashiero Jul 31, 2026
0635402
fix(cli): /sessions search — full session ID, wider preview (40 chars)
Esashiero Jul 31, 2026
1549b76
fix(cli): review pass — remove duplicate headers, dead code, unused i…
Esashiero Jul 31, 2026
3515a5e
feat(cli): one canonical sessions table across all four surfaces
Esashiero Jul 31, 2026
9a97da7
feat(cli): --limit for sessions search + help mentions new options
Esashiero Jul 31, 2026
de3d85c
feat(cli): -l shorthand for --limit; trim all/full from help footers
Esashiero Jul 31, 2026
a9b64f2
feat(cli): search-result numbers are resumable; align listing default…
Esashiero Jul 31, 2026
1197032
feat(cli): search # column shows the canonical sessions-list rank
Esashiero Jul 31, 2026
ae0ce27
fix(cli): chain-aware rank resolution in sessions search # column
Esashiero Jul 31, 2026
1161e53
fix(cli): collapse all compression generations in search dedup + Tok(…
Esashiero Jul 31, 2026
a7f2092
fix(cli): Created column shows original conversation start (root)
Esashiero Jul 31, 2026
0df3943
feat(cli): paginated sessions list + /resume list <page>, default lim…
Esashiero Jul 31, 2026
9805886
feat(cli): concise parameter hints on listings, full reference in --help
Esashiero Jul 31, 2026
c81da69
bd init: initialize beads issue tracking
Esashiero Jul 31, 2026
a904a54
fix(cli): bare-number resume resolves global ranks on any page
Esashiero Jul 31, 2026
e1996bc
fix(cli): search Last column + sort use the listing's last_active def…
Esashiero Jul 31, 2026
a3c7eaf
fix(cli): Tok(ΣIn/ΣOut) shows the compression-chain total
Esashiero Jul 31, 2026
d7e65e1
fix(cli): plain-list previews resolve through the chain root
Esashiero Jul 31, 2026
cbdae2c
fix(cli): session_rank walks through the canonical compression tip
Esashiero Jul 31, 2026
32eaaef
fix(cli): _compression_root stops at delegate and tool children
Esashiero Jul 31, 2026
f5cf0fe
test(cli): real-DB resume arming for numbered selection
Esashiero Jul 31, 2026
7633831
fix(cli): delete dead /sessions page-parse branch
Esashiero Jul 31, 2026
b66f8cd
fix(cli): workspace-filtered listings paginate in Python
Esashiero Jul 31, 2026
934cca8
fix(cli): warn on invalid --limit instead of failing silently
Esashiero Jul 31, 2026
70ccb15
refactor(cli): unify lineage walker hop caps under one constant
Esashiero Jul 31, 2026
5858226
refactor(cli): one shared search pipeline for CLI and /sessions search
Esashiero Jul 31, 2026
23886f1
fix(gateway): /resume and /sessions share CLI listing semantics
Esashiero Jul 31, 2026
c80e132
Merge remote-tracking branch 'origin/main' into sessions-resume-impro…
Esashiero Jul 31, 2026
9a63c6c
fix(cli): restore rich sessions list with pagination on merged main
Esashiero Jul 31, 2026
48b1b0e
chore: drop .beads/.backups/plan artifacts from PR branch
Esashiero Jul 31, 2026
6de17ee
chore: revert AGENTS.md and .gitignore to upstream (drop bd integration)
Esashiero Jul 31, 2026
3ad71ba
fix(search): project ancestor hits to tip, edge-aware preview walk
Esashiero Jul 31, 2026
e5f223f
Merge sessions-resume-improvements into current main (restore improve…
Esashiero Aug 20, 2026
0ea1610
fix(gateway): restore lane-scoping in /sessions and numbered /resume …
Esashiero Aug 20, 2026
70aa009
refactor: pin chain-token CTE depth to COMPRESSION_CHAIN_MAX_HOPS and…
Esashiero Aug 20, 2026
30bd45c
fix(sessions): lane-scope FTS5 search candidate pools via session_key
Esashiero Aug 20, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
344 changes: 344 additions & 0 deletions .backups/sessions-resume-improvements-review.md.20260731_133808.bak

Large diffs are not rendered by default.

344 changes: 344 additions & 0 deletions .backups/sessions-resume-improvements-review.md.20260731_142508.bak

Large diffs are not rendered by default.

344 changes: 344 additions & 0 deletions .backups/sessions-resume-improvements-review.md.20260731_142517.bak

Large diffs are not rendered by default.

344 changes: 344 additions & 0 deletions .backups/sessions-resume-improvements-review.md.20260731_142524.bak

Large diffs are not rendered by default.

344 changes: 344 additions & 0 deletions .backups/sessions-resume-improvements-review.md.20260731_142531.bak

Large diffs are not rendered by default.

346 changes: 346 additions & 0 deletions .backups/sessions-resume-improvements-review.md.20260731_142544.bak

Large diffs are not rendered by default.

346 changes: 346 additions & 0 deletions .backups/sessions-resume-improvements-review.md.20260731_142555.bak

Large diffs are not rendered by default.

51 changes: 51 additions & 0 deletions .beads/.gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,51 @@
# Dolt database (managed by Dolt, not git)
dolt/
dolt-access.lock

# Runtime files
bd.sock
bd.sock.startlock
sync-state.json
last-touched

# Local version tracking (prevents upgrade notification spam after git ops)
.local_version

# Worktree redirect file (contains relative path to main repo's .beads/)
# Must not be committed as paths would be wrong in other clones
redirect

# Sync state (local-only, per-machine)
# These files are machine-specific and should not be shared across clones
.sync.lock
export-state/

# Ephemeral store (SQLite - wisps/molecules, intentionally not versioned)
ephemeral.sqlite3
ephemeral.sqlite3-journal
ephemeral.sqlite3-wal
ephemeral.sqlite3-shm

# Dolt server management (auto-started by bd)
dolt-server.pid
dolt-server.log
dolt-server.lock
dolt-server.port
dolt-server.activity
dolt-monitor.pid

# Backup data (auto-exported JSONL, local-only)
backup/

# Legacy files (from pre-Dolt versions)
*.db
*.db?*
*.db-journal
*.db-wal
*.db-shm
db.sqlite
bd.db
# NOTE: Do NOT add negation patterns here.
# They would override fork protection in .git/info/exclude.
# Config files (metadata.json, config.yaml) are tracked by git by default
# since no pattern above ignores them.
81 changes: 81 additions & 0 deletions .beads/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,81 @@
# Beads - AI-Native Issue Tracking

Welcome to Beads! This repository uses **Beads** for issue tracking - a modern, AI-native tool designed to live directly in your codebase alongside your code.

## What is Beads?

Beads is issue tracking that lives in your repo, making it perfect for AI coding agents and developers who want their issues close to their code. No web UI required - everything works through the CLI and integrates seamlessly with git.

**Learn more:** [github.com/steveyegge/beads](https://github.com/steveyegge/beads)

## Quick Start

### Essential Commands

```bash
# Create new issues
bd create "Add user authentication"

# View all issues
bd list

# View issue details
bd show <issue-id>

# Update issue status
bd update <issue-id> --claim
bd update <issue-id> --status done

# Sync with Dolt remote
bd dolt push
```

### Working with Issues

Issues in Beads are:
- **Git-native**: Stored in Dolt database with version control and branching
- **AI-friendly**: CLI-first design works perfectly with AI coding agents
- **Branch-aware**: Issues can follow your branch workflow
- **Always in sync**: Auto-syncs with your commits

## Why Beads?

✨ **AI-Native Design**
- Built specifically for AI-assisted development workflows
- CLI-first interface works seamlessly with AI coding agents
- No context switching to web UIs

🚀 **Developer Focused**
- Issues live in your repo, right next to your code
- Works offline, syncs when you push
- Fast, lightweight, and stays out of your way

🔧 **Git Integration**
- Automatic sync with git commits
- Branch-aware issue tracking
- Dolt-native three-way merge resolution

## Get Started with Beads

Try Beads in your own projects:

```bash
# Install Beads
curl -sSL https://raw.githubusercontent.com/steveyegge/beads/main/scripts/install.sh | bash

# Initialize in your repo
bd init

# Create your first issue
bd create "Try out Beads"
```

## Learn More

- **Documentation**: [github.com/steveyegge/beads/docs](https://github.com/steveyegge/beads/tree/main/docs)
- **Quick Start Guide**: Run `bd quickstart`
- **Examples**: [github.com/steveyegge/beads/examples](https://github.com/steveyegge/beads/tree/main/examples)

---

*Beads: Issue tracking that moves at the speed of thought* ⚡
54 changes: 54 additions & 0 deletions .beads/config.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,54 @@
# Beads Configuration File
# This file configures default behavior for all bd commands in this repository
# All settings can also be set via environment variables (BD_* prefix)
# or overridden with command-line flags

# Issue prefix for this repository (used by bd init)
# If not set, bd init will auto-detect from directory name
# Example: issue-prefix: "myproject" creates issues like "myproject-1", "myproject-2", etc.
# issue-prefix: ""

# Use no-db mode: JSONL-only, no Dolt database
# When true, bd will use .beads/issues.jsonl as the source of truth
# no-db: false

# Enable JSON output by default
# json: false

# Feedback title formatting for mutating commands (create/update/close/dep/edit)
# 0 = hide titles, N > 0 = truncate to N characters
# output:
# title-length: 255

# Default actor for audit trails (overridden by BD_ACTOR or --actor)
# actor: ""

# Export events (audit trail) to .beads/events.jsonl on each flush/sync
# When enabled, new events are appended incrementally using a high-water mark.
# Use 'bd export --events' to trigger manually regardless of this setting.
# events-export: false

# Multi-repo configuration (experimental - bd-307)
# Allows hydrating from multiple repositories and routing writes to the correct database
# repos:
# primary: "." # Primary repo (where this database lives)
# additional: # Additional repos to hydrate from (read-only)
# - ~/beads-planning # Personal planning repo
# - ~/work-planning # Work planning repo

# JSONL backup (periodic export for off-machine recovery)
# Auto-enabled when a git remote exists. Override explicitly:
# backup:
# enabled: false # Disable auto-backup entirely
# interval: 15m # Minimum time between auto-exports
# git-push: false # Disable git push (export locally only)
# git-repo: "" # Separate git repo for backups (default: project repo)

# Integration settings (access with 'bd config get/set')
# These are stored in the database, not in this file:
# - jira.url
# - jira.project
# - linear.url
# - linear.api-key
# - github.org
# - github.repo
9 changes: 9 additions & 0 deletions .beads/hooks/post-checkout
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
#!/usr/bin/env sh
# --- BEGIN BEADS INTEGRATION v0.59.0 ---
# This section is managed by beads. Do not remove these markers.
if command -v bd >/dev/null 2>&1; then
export BD_GIT_HOOK=1
bd hooks run post-checkout "$@"
_bd_exit=$?; if [ $_bd_exit -ne 0 ]; then exit $_bd_exit; fi
fi
# --- END BEADS INTEGRATION v0.59.0 ---
9 changes: 9 additions & 0 deletions .beads/hooks/post-merge
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
#!/usr/bin/env sh
# --- BEGIN BEADS INTEGRATION v0.59.0 ---
# This section is managed by beads. Do not remove these markers.
if command -v bd >/dev/null 2>&1; then
export BD_GIT_HOOK=1
bd hooks run post-merge "$@"
_bd_exit=$?; if [ $_bd_exit -ne 0 ]; then exit $_bd_exit; fi
fi
# --- END BEADS INTEGRATION v0.59.0 ---
9 changes: 9 additions & 0 deletions .beads/hooks/pre-commit
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
#!/usr/bin/env sh
# --- BEGIN BEADS INTEGRATION v0.59.0 ---
# This section is managed by beads. Do not remove these markers.
if command -v bd >/dev/null 2>&1; then
export BD_GIT_HOOK=1
bd hooks run pre-commit "$@"
Comment thread
Esashiero marked this conversation as resolved.
Resolved
_bd_exit=$?; if [ $_bd_exit -ne 0 ]; then exit $_bd_exit; fi
fi
# --- END BEADS INTEGRATION v0.59.0 ---
9 changes: 9 additions & 0 deletions .beads/hooks/pre-push
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
#!/usr/bin/env sh
# --- BEGIN BEADS INTEGRATION v0.59.0 ---
# This section is managed by beads. Do not remove these markers.
if command -v bd >/dev/null 2>&1; then
export BD_GIT_HOOK=1
bd hooks run pre-push "$@"
_bd_exit=$?; if [ $_bd_exit -ne 0 ]; then exit $_bd_exit; fi
fi
# --- END BEADS INTEGRATION v0.59.0 ---
9 changes: 9 additions & 0 deletions .beads/hooks/prepare-commit-msg
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
#!/usr/bin/env sh
# --- BEGIN BEADS INTEGRATION v0.59.0 ---
# This section is managed by beads. Do not remove these markers.
if command -v bd >/dev/null 2>&1; then
export BD_GIT_HOOK=1
bd hooks run prepare-commit-msg "$@"
_bd_exit=$?; if [ $_bd_exit -ne 0 ]; then exit $_bd_exit; fi
fi
# --- END BEADS INTEGRATION v0.59.0 ---
Empty file added .beads/interactions.jsonl
Empty file.
7 changes: 7 additions & 0 deletions .beads/metadata.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
{
"database": "dolt",
"backend": "dolt",
"dolt_mode": "server",
"dolt_database": "hermes_agent",
"project_id": "50e1949f-d704-4b4e-b28a-23a799e9874c"
}
5 changes: 5 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -190,6 +190,11 @@ infographics/
infograficos/
infografico/
native/fts5_cjk/*.so

# Dolt database files (added by bd init)
.dolt/
*.db

# Runtime marker written by hermes update when a lazy dependency refresh is
# interrupted; consumed by launch-time recovery. Never commit it (was tracked
# by accident via 3a69e34702, removed in the #72002 salvage).
Expand Down
113 changes: 113 additions & 0 deletions AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -1433,3 +1433,116 @@ test('windowsHide defaults to true on Windows, is left alone elsewhere', () => {
If the logic lives inline in a god-file (`main.ts`, `cli.py`,
`gateway/run.py`) and extracting it feels disruptive: that's the actual
signal to do the extraction, not to regex around it.

<!-- BEGIN BEADS INTEGRATION -->
## Issue Tracking with bd (beads)

**IMPORTANT**: This project uses **bd (beads)** for ALL issue tracking. Do NOT use markdown TODOs, task lists, or other tracking methods.

### Why bd?

- Dependency-aware: Track blockers and relationships between issues
- Git-friendly: Dolt-powered version control with native sync
- Agent-optimized: JSON output, ready work detection, discovered-from links
- Prevents duplicate tracking systems and confusion

### Quick Start

**Check for ready work:**

```bash
bd ready --json
```

**Create new issues:**

```bash
bd create "Issue title" --description="Detailed context" -t bug|feature|task -p 0-4 --json
bd create "Issue title" --description="What this issue is about" -p 1 --deps discovered-from:bd-123 --json
```

**Claim and update:**

```bash
bd update <id> --claim --json
bd update bd-42 --priority 1 --json
```

**Complete work:**

```bash
bd close bd-42 --reason "Completed" --json
```

### Issue Types

- `bug` - Something broken
- `feature` - New functionality
- `task` - Work item (tests, docs, refactoring)
- `epic` - Large feature with subtasks
- `chore` - Maintenance (dependencies, tooling)

### Priorities

- `0` - Critical (security, data loss, broken builds)
- `1` - High (major features, important bugs)
- `2` - Medium (default, nice-to-have)
- `3` - Low (polish, optimization)
- `4` - Backlog (future ideas)

### Workflow for AI Agents

1. **Check ready work**: `bd ready` shows unblocked issues
2. **Claim your task atomically**: `bd update <id> --claim`
3. **Work on it**: Implement, test, document
4. **Discover new work?** Create linked issue:
- `bd create "Found bug" --description="Details about what was found" -p 1 --deps discovered-from:<parent-id>`
5. **Complete**: `bd close <id> --reason "Done"`

### Auto-Sync

bd automatically syncs via Dolt:

- Each write auto-commits to Dolt history
- Use `bd dolt push`/`bd dolt pull` for remote sync
- No manual export/import needed!

### Important Rules

- ✅ Use bd for ALL task tracking
- ✅ Always use `--json` flag for programmatic use
- ✅ Link discovered work with `discovered-from` dependencies
- ✅ Check `bd ready` before asking "what should I work on?"
- ❌ Do NOT create markdown TODO lists
- ❌ Do NOT use external issue trackers
- ❌ Do NOT duplicate tracking systems

For more details, see README.md and docs/QUICKSTART.md.

## Landing the Plane (Session Completion)

**When ending a work session**, you MUST complete ALL steps below. Work is NOT complete until `git push` succeeds.

**MANDATORY WORKFLOW:**

1. **File issues for remaining work** - Create issues for anything that needs follow-up
2. **Run quality gates** (if code changed) - Tests, linters, builds
3. **Update issue status** - Close finished work, update in-progress items
4. **PUSH TO REMOTE** - This is MANDATORY:
```bash
git pull --rebase
bd sync
git push
git status # MUST show "up to date with origin"
```
5. **Clean up** - Clear stashes, prune remote branches
6. **Verify** - All changes committed AND pushed
7. **Hand off** - Provide context for next session

**CRITICAL RULES:**
- Work is NOT complete until `git push` succeeds
- NEVER stop before pushing - that leaves work stranded locally
- NEVER say "ready to push when you are" - YOU must push
- If push fails, resolve and retry until it succeeds

<!-- END BEADS INTEGRATION -->
Loading