Small
wget like mirroring utility.
Add beads ticket for optional output with smart URL-based naming
+198
+45
.beads/.gitignore
+45
.beads/.gitignore
···
1
+
# SQLite databases
2
+
*.db
3
+
*.db?*
4
+
*.db-journal
5
+
*.db-wal
6
+
*.db-shm
7
+
8
+
# Daemon runtime files
9
+
daemon.lock
10
+
daemon.log
11
+
daemon.pid
12
+
bd.sock
13
+
sync-state.json
14
+
last-touched
15
+
16
+
# Local version tracking (prevents upgrade notification spam after git ops)
17
+
.local_version
18
+
19
+
# Legacy database files
20
+
db.sqlite
21
+
bd.db
22
+
23
+
# Worktree redirect file (contains relative path to main repo's .beads/)
24
+
# Must not be committed as paths would be wrong in other clones
25
+
redirect
26
+
27
+
# Merge artifacts (temporary files from 3-way merge)
28
+
beads.base.jsonl
29
+
beads.base.meta.json
30
+
beads.left.jsonl
31
+
beads.left.meta.json
32
+
beads.right.jsonl
33
+
beads.right.meta.json
34
+
35
+
# Sync state (local-only, per-machine)
36
+
# These files are machine-specific and should not be shared across clones
37
+
.sync.lock
38
+
sync_base.jsonl
39
+
export-state/
40
+
41
+
# NOTE: Do NOT add negation patterns (e.g., !issues.jsonl) here.
42
+
# They would override fork protection in .git/info/exclude, allowing
43
+
# contributors to accidentally commit upstream issue databases.
44
+
# The JSONL files (issues.jsonl, interactions.jsonl) and config files
45
+
# are tracked by git by default since no pattern above ignores them.
+81
.beads/README.md
+81
.beads/README.md
···
1
+
# Beads - AI-Native Issue Tracking
2
+
3
+
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.
4
+
5
+
## What is Beads?
6
+
7
+
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.
8
+
9
+
**Learn more:** [github.com/steveyegge/beads](https://github.com/steveyegge/beads)
10
+
11
+
## Quick Start
12
+
13
+
### Essential Commands
14
+
15
+
```bash
16
+
# Create new issues
17
+
bd create "Add user authentication"
18
+
19
+
# View all issues
20
+
bd list
21
+
22
+
# View issue details
23
+
bd show <issue-id>
24
+
25
+
# Update issue status
26
+
bd update <issue-id> --status in_progress
27
+
bd update <issue-id> --status done
28
+
29
+
# Sync with git remote
30
+
bd sync
31
+
```
32
+
33
+
### Working with Issues
34
+
35
+
Issues in Beads are:
36
+
- **Git-native**: Stored in `.beads/issues.jsonl` and synced like code
37
+
- **AI-friendly**: CLI-first design works perfectly with AI coding agents
38
+
- **Branch-aware**: Issues can follow your branch workflow
39
+
- **Always in sync**: Auto-syncs with your commits
40
+
41
+
## Why Beads?
42
+
43
+
✨ **AI-Native Design**
44
+
- Built specifically for AI-assisted development workflows
45
+
- CLI-first interface works seamlessly with AI coding agents
46
+
- No context switching to web UIs
47
+
48
+
🚀 **Developer Focused**
49
+
- Issues live in your repo, right next to your code
50
+
- Works offline, syncs when you push
51
+
- Fast, lightweight, and stays out of your way
52
+
53
+
🔧 **Git Integration**
54
+
- Automatic sync with git commits
55
+
- Branch-aware issue tracking
56
+
- Intelligent JSONL merge resolution
57
+
58
+
## Get Started with Beads
59
+
60
+
Try Beads in your own projects:
61
+
62
+
```bash
63
+
# Install Beads
64
+
curl -sSL https://raw.githubusercontent.com/steveyegge/beads/main/scripts/install.sh | bash
65
+
66
+
# Initialize in your repo
67
+
bd init
68
+
69
+
# Create your first issue
70
+
bd create "Try out Beads"
71
+
```
72
+
73
+
## Learn More
74
+
75
+
- **Documentation**: [github.com/steveyegge/beads/docs](https://github.com/steveyegge/beads/tree/main/docs)
76
+
- **Quick Start Guide**: Run `bd quickstart`
77
+
- **Examples**: [github.com/steveyegge/beads/examples](https://github.com/steveyegge/beads/tree/main/examples)
78
+
79
+
---
80
+
81
+
*Beads: Issue tracking that moves at the speed of thought* ⚡
+67
.beads/config.yaml
+67
.beads/config.yaml
···
1
+
# Beads Configuration File
2
+
# This file configures default behavior for all bd commands in this repository
3
+
# All settings can also be set via environment variables (BD_* prefix)
4
+
# or overridden with command-line flags
5
+
6
+
# Issue prefix for this repository (used by bd init)
7
+
# If not set, bd init will auto-detect from directory name
8
+
# Example: issue-prefix: "myproject" creates issues like "myproject-1", "myproject-2", etc.
9
+
# issue-prefix: ""
10
+
11
+
# Use no-db mode: load from JSONL, no SQLite, write back after each command
12
+
# When true, bd will use .beads/issues.jsonl as the source of truth
13
+
# instead of SQLite database
14
+
# no-db: false
15
+
16
+
# Disable daemon for RPC communication (forces direct database access)
17
+
# no-daemon: false
18
+
19
+
# Disable auto-flush of database to JSONL after mutations
20
+
# no-auto-flush: false
21
+
22
+
# Disable auto-import from JSONL when it's newer than database
23
+
# no-auto-import: false
24
+
25
+
# Enable JSON output by default
26
+
# json: false
27
+
28
+
# Default actor for audit trails (overridden by BD_ACTOR or --actor)
29
+
# actor: ""
30
+
31
+
# Path to database (overridden by BEADS_DB or --db)
32
+
# db: ""
33
+
34
+
# Auto-start daemon if not running (can also use BEADS_AUTO_START_DAEMON)
35
+
# auto-start-daemon: true
36
+
37
+
# Debounce interval for auto-flush (can also use BEADS_FLUSH_DEBOUNCE)
38
+
# flush-debounce: "5s"
39
+
40
+
# Export events (audit trail) to .beads/events.jsonl on each flush/sync
41
+
# When enabled, new events are appended incrementally using a high-water mark.
42
+
# Use 'bd export --events' to trigger manually regardless of this setting.
43
+
# events-export: false
44
+
45
+
# Git branch for beads commits (bd sync will commit to this branch)
46
+
# IMPORTANT: Set this for team projects so all clones use the same sync branch.
47
+
# This setting persists across clones (unlike database config which is gitignored).
48
+
# Can also use BEADS_SYNC_BRANCH env var for local override.
49
+
# If not set, bd sync will require you to run 'bd config set sync.branch <branch>'.
50
+
# sync-branch: "beads-sync"
51
+
52
+
# Multi-repo configuration (experimental - bd-307)
53
+
# Allows hydrating from multiple repositories and routing writes to the correct JSONL
54
+
# repos:
55
+
# primary: "." # Primary repo (where this database lives)
56
+
# additional: # Additional repos to hydrate from (read-only)
57
+
# - ~/beads-planning # Personal planning repo
58
+
# - ~/work-planning # Work planning repo
59
+
60
+
# Integration settings (access with 'bd config get/set')
61
+
# These are stored in the database, not in this file:
62
+
# - jira.url
63
+
# - jira.project
64
+
# - linear.url
65
+
# - linear.api-key
66
+
# - github.org
67
+
# - github.repo
.beads/interactions.jsonl
.beads/interactions.jsonl
This is a binary file and will not be displayed.
+1
.beads/issues.jsonl
+1
.beads/issues.jsonl
···
1
+
{"id":"de-optional-output-smart-url-naming","title":"Make output directory optional with smart URL-based naming","description":"Currently, output directory is required. We should make it optional and support a special value (e.g., `true` or `auto`) that uses the URL to determine the output directory name.\n\nThe `getDefaultOutput()` function already implements smart directory naming:\n- `https://deepwiki.com/open-telemetry/otel-arrow` → `otel-arrow`\n- `https://deepwiki.com/` → `deepwiki.com`\n\n## Requirements\n\n1. Make `--output` argument optional (currently required)\n2. Support special value `--output true` or `--output auto` that enables smart naming\n3. When multiple URLs are provided with smart naming enabled, each URL should get its own subdirectory:\n - `node cli.ts https://example.com/foo https://example.com/bar --output true`\n - Creates: `./foo/` and `./bar/` in current working directory\n\n## Open Questions\n\n- How should this work when mixing custom output dir with smart naming?\n - Should `--output ./output true` be invalid?\n - Or should it create `./output/foo/`?\n- What about hash fragments in URLs?\n - Should `https://example.com/page#section` use `page` or `page#section`?","status":"open","priority":2,"issue_type":"task","owner":"rektide+git@voodoowarez.com","created_at":"2026-02-09T20:07:27.284140403-05:00","created_by":"rektide de la faye","updated_at":"2026-02-09T20:07:27.284140403-05:00"}