Testing a small http-client on Linux using no_std & embedded reqwless.
bd init: initialize beads issue tracking
+467
+51
.beads/.gitignore
+51
.beads/.gitignore
···
1
+
# Dolt database (managed by Dolt, not git)
2
+
dolt/
3
+
dolt-access.lock
4
+
5
+
# Runtime files
6
+
bd.sock
7
+
bd.sock.startlock
8
+
sync-state.json
9
+
last-touched
10
+
11
+
# Local version tracking (prevents upgrade notification spam after git ops)
12
+
.local_version
13
+
14
+
# Worktree redirect file (contains relative path to main repo's .beads/)
15
+
# Must not be committed as paths would be wrong in other clones
16
+
redirect
17
+
18
+
# Sync state (local-only, per-machine)
19
+
# These files are machine-specific and should not be shared across clones
20
+
.sync.lock
21
+
export-state/
22
+
23
+
# Ephemeral store (SQLite - wisps/molecules, intentionally not versioned)
24
+
ephemeral.sqlite3
25
+
ephemeral.sqlite3-journal
26
+
ephemeral.sqlite3-wal
27
+
ephemeral.sqlite3-shm
28
+
29
+
# Dolt server management (auto-started by bd)
30
+
dolt-server.pid
31
+
dolt-server.log
32
+
dolt-server.lock
33
+
dolt-server.port
34
+
dolt-server.activity
35
+
dolt-monitor.pid
36
+
37
+
# Backup data (auto-exported JSONL, local-only)
38
+
backup/
39
+
40
+
# Legacy files (from pre-Dolt versions)
41
+
*.db
42
+
*.db?*
43
+
*.db-journal
44
+
*.db-wal
45
+
*.db-shm
46
+
db.sqlite
47
+
bd.db
48
+
# NOTE: Do NOT add negation patterns here.
49
+
# They would override fork protection in .git/info/exclude.
50
+
# Config files (metadata.json, config.yaml) are tracked by git by default
51
+
# 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> --claim
27
+
bd update <issue-id> --status done
28
+
29
+
# Sync with Dolt remote
30
+
bd dolt push
31
+
```
32
+
33
+
### Working with Issues
34
+
35
+
Issues in Beads are:
36
+
- **Git-native**: Stored in Dolt database with version control and branching
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
+
- Dolt-native three-way 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* ⚡
+54
.beads/config.yaml
+54
.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: JSONL-only, no Dolt database
12
+
# When true, bd will use .beads/issues.jsonl as the source of truth
13
+
# no-db: false
14
+
15
+
# Enable JSON output by default
16
+
# json: false
17
+
18
+
# Feedback title formatting for mutating commands (create/update/close/dep/edit)
19
+
# 0 = hide titles, N > 0 = truncate to N characters
20
+
# output:
21
+
# title-length: 255
22
+
23
+
# Default actor for audit trails (overridden by BD_ACTOR or --actor)
24
+
# actor: ""
25
+
26
+
# Export events (audit trail) to .beads/events.jsonl on each flush/sync
27
+
# When enabled, new events are appended incrementally using a high-water mark.
28
+
# Use 'bd export --events' to trigger manually regardless of this setting.
29
+
# events-export: false
30
+
31
+
# Multi-repo configuration (experimental - bd-307)
32
+
# Allows hydrating from multiple repositories and routing writes to the correct database
33
+
# repos:
34
+
# primary: "." # Primary repo (where this database lives)
35
+
# additional: # Additional repos to hydrate from (read-only)
36
+
# - ~/beads-planning # Personal planning repo
37
+
# - ~/work-planning # Work planning repo
38
+
39
+
# JSONL backup (periodic export for off-machine recovery)
40
+
# Auto-enabled when a git remote exists. Override explicitly:
41
+
# backup:
42
+
# enabled: false # Disable auto-backup entirely
43
+
# interval: 15m # Minimum time between auto-exports
44
+
# git-push: false # Disable git push (export locally only)
45
+
# git-repo: "" # Separate git repo for backups (default: project repo)
46
+
47
+
# Integration settings (access with 'bd config get/set')
48
+
# These are stored in the database, not in this file:
49
+
# - jira.url
50
+
# - jira.project
51
+
# - linear.url
52
+
# - linear.api-key
53
+
# - github.org
54
+
# - github.repo
.beads/dolt-monitor.pid.lock
.beads/dolt-monitor.pid.lock
This is a binary file and will not be displayed.
+24
.beads/hooks/post-checkout
+24
.beads/hooks/post-checkout
···
1
+
#!/usr/bin/env sh
2
+
# --- BEGIN BEADS INTEGRATION v0.59.0 ---
3
+
# This section is managed by beads. Do not remove these markers.
4
+
if command -v bd >/dev/null 2>&1; then
5
+
export BD_GIT_HOOK=1
6
+
_bd_timeout=${BEADS_HOOK_TIMEOUT:-30}
7
+
if command -v timeout >/dev/null 2>&1; then
8
+
timeout "$_bd_timeout" bd hooks run post-checkout "$@"
9
+
_bd_exit=$?
10
+
if [ $_bd_exit -eq 124 ]; then
11
+
echo >&2 "beads: hook 'post-checkout' timed out after ${_bd_timeout}s — continuing without beads"
12
+
_bd_exit=0
13
+
fi
14
+
else
15
+
bd hooks run post-checkout "$@"
16
+
_bd_exit=$?
17
+
fi
18
+
if [ $_bd_exit -eq 3 ]; then
19
+
echo >&2 "beads: database not initialized — skipping hook 'post-checkout'"
20
+
_bd_exit=0
21
+
fi
22
+
if [ $_bd_exit -ne 0 ]; then exit $_bd_exit; fi
23
+
fi
24
+
# --- END BEADS INTEGRATION v0.59.0 ---
+24
.beads/hooks/post-merge
+24
.beads/hooks/post-merge
···
1
+
#!/usr/bin/env sh
2
+
# --- BEGIN BEADS INTEGRATION v0.59.0 ---
3
+
# This section is managed by beads. Do not remove these markers.
4
+
if command -v bd >/dev/null 2>&1; then
5
+
export BD_GIT_HOOK=1
6
+
_bd_timeout=${BEADS_HOOK_TIMEOUT:-30}
7
+
if command -v timeout >/dev/null 2>&1; then
8
+
timeout "$_bd_timeout" bd hooks run post-merge "$@"
9
+
_bd_exit=$?
10
+
if [ $_bd_exit -eq 124 ]; then
11
+
echo >&2 "beads: hook 'post-merge' timed out after ${_bd_timeout}s — continuing without beads"
12
+
_bd_exit=0
13
+
fi
14
+
else
15
+
bd hooks run post-merge "$@"
16
+
_bd_exit=$?
17
+
fi
18
+
if [ $_bd_exit -eq 3 ]; then
19
+
echo >&2 "beads: database not initialized — skipping hook 'post-merge'"
20
+
_bd_exit=0
21
+
fi
22
+
if [ $_bd_exit -ne 0 ]; then exit $_bd_exit; fi
23
+
fi
24
+
# --- END BEADS INTEGRATION v0.59.0 ---
+24
.beads/hooks/pre-commit
+24
.beads/hooks/pre-commit
···
1
+
#!/usr/bin/env sh
2
+
# --- BEGIN BEADS INTEGRATION v0.59.0 ---
3
+
# This section is managed by beads. Do not remove these markers.
4
+
if command -v bd >/dev/null 2>&1; then
5
+
export BD_GIT_HOOK=1
6
+
_bd_timeout=${BEADS_HOOK_TIMEOUT:-30}
7
+
if command -v timeout >/dev/null 2>&1; then
8
+
timeout "$_bd_timeout" bd hooks run pre-commit "$@"
9
+
_bd_exit=$?
10
+
if [ $_bd_exit -eq 124 ]; then
11
+
echo >&2 "beads: hook 'pre-commit' timed out after ${_bd_timeout}s — continuing without beads"
12
+
_bd_exit=0
13
+
fi
14
+
else
15
+
bd hooks run pre-commit "$@"
16
+
_bd_exit=$?
17
+
fi
18
+
if [ $_bd_exit -eq 3 ]; then
19
+
echo >&2 "beads: database not initialized — skipping hook 'pre-commit'"
20
+
_bd_exit=0
21
+
fi
22
+
if [ $_bd_exit -ne 0 ]; then exit $_bd_exit; fi
23
+
fi
24
+
# --- END BEADS INTEGRATION v0.59.0 ---
+24
.beads/hooks/pre-push
+24
.beads/hooks/pre-push
···
1
+
#!/usr/bin/env sh
2
+
# --- BEGIN BEADS INTEGRATION v0.59.0 ---
3
+
# This section is managed by beads. Do not remove these markers.
4
+
if command -v bd >/dev/null 2>&1; then
5
+
export BD_GIT_HOOK=1
6
+
_bd_timeout=${BEADS_HOOK_TIMEOUT:-30}
7
+
if command -v timeout >/dev/null 2>&1; then
8
+
timeout "$_bd_timeout" bd hooks run pre-push "$@"
9
+
_bd_exit=$?
10
+
if [ $_bd_exit -eq 124 ]; then
11
+
echo >&2 "beads: hook 'pre-push' timed out after ${_bd_timeout}s — continuing without beads"
12
+
_bd_exit=0
13
+
fi
14
+
else
15
+
bd hooks run pre-push "$@"
16
+
_bd_exit=$?
17
+
fi
18
+
if [ $_bd_exit -eq 3 ]; then
19
+
echo >&2 "beads: database not initialized — skipping hook 'pre-push'"
20
+
_bd_exit=0
21
+
fi
22
+
if [ $_bd_exit -ne 0 ]; then exit $_bd_exit; fi
23
+
fi
24
+
# --- END BEADS INTEGRATION v0.59.0 ---
+24
.beads/hooks/prepare-commit-msg
+24
.beads/hooks/prepare-commit-msg
···
1
+
#!/usr/bin/env sh
2
+
# --- BEGIN BEADS INTEGRATION v0.59.0 ---
3
+
# This section is managed by beads. Do not remove these markers.
4
+
if command -v bd >/dev/null 2>&1; then
5
+
export BD_GIT_HOOK=1
6
+
_bd_timeout=${BEADS_HOOK_TIMEOUT:-30}
7
+
if command -v timeout >/dev/null 2>&1; then
8
+
timeout "$_bd_timeout" bd hooks run prepare-commit-msg "$@"
9
+
_bd_exit=$?
10
+
if [ $_bd_exit -eq 124 ]; then
11
+
echo >&2 "beads: hook 'prepare-commit-msg' timed out after ${_bd_timeout}s — continuing without beads"
12
+
_bd_exit=0
13
+
fi
14
+
else
15
+
bd hooks run prepare-commit-msg "$@"
16
+
_bd_exit=$?
17
+
fi
18
+
if [ $_bd_exit -eq 3 ]; then
19
+
echo >&2 "beads: database not initialized — skipping hook 'prepare-commit-msg'"
20
+
_bd_exit=0
21
+
fi
22
+
if [ $_bd_exit -ne 0 ]; then exit $_bd_exit; fi
23
+
fi
24
+
# --- END BEADS INTEGRATION v0.59.0 ---
.beads/interactions.jsonl
.beads/interactions.jsonl
This is a binary file and will not be displayed.
+7
.beads/metadata.json
+7
.beads/metadata.json
+150
AGENTS.md
+150
AGENTS.md
···
1
+
# Agent Instructions
2
+
3
+
This project uses **bd** (beads) for issue tracking. Run `bd onboard` to get started.
4
+
5
+
## Quick Reference
6
+
7
+
```bash
8
+
bd ready # Find available work
9
+
bd show <id> # View issue details
10
+
bd update <id> --claim # Claim work atomically
11
+
bd close <id> # Complete work
12
+
bd sync # Sync with git
13
+
```
14
+
15
+
## Non-Interactive Shell Commands
16
+
17
+
**ALWAYS use non-interactive flags** with file operations to avoid hanging on confirmation prompts.
18
+
19
+
Shell commands like `cp`, `mv`, and `rm` may be aliased to include `-i` (interactive) mode on some systems, causing the agent to hang indefinitely waiting for y/n input.
20
+
21
+
**Use these forms instead:**
22
+
```bash
23
+
# Force overwrite without prompting
24
+
cp -f source dest # NOT: cp source dest
25
+
mv -f source dest # NOT: mv source dest
26
+
rm -f file # NOT: rm file
27
+
28
+
# For recursive operations
29
+
rm -rf directory # NOT: rm -r directory
30
+
cp -rf source dest # NOT: cp -r source dest
31
+
```
32
+
33
+
**Other commands that may prompt:**
34
+
- `scp` - use `-o BatchMode=yes` for non-interactive
35
+
- `ssh` - use `-o BatchMode=yes` to fail instead of prompting
36
+
- `apt-get` - use `-y` flag
37
+
- `brew` - use `HOMEBREW_NO_AUTO_UPDATE=1` env var
38
+
39
+
<!-- BEGIN BEADS INTEGRATION -->
40
+
## Issue Tracking with bd (beads)
41
+
42
+
**IMPORTANT**: This project uses **bd (beads)** for ALL issue tracking. Do NOT use markdown TODOs, task lists, or other tracking methods.
43
+
44
+
### Why bd?
45
+
46
+
- Dependency-aware: Track blockers and relationships between issues
47
+
- Version-controlled: Built on Dolt with cell-level merge
48
+
- Agent-optimized: JSON output, ready work detection, discovered-from links
49
+
- Prevents duplicate tracking systems and confusion
50
+
51
+
### Quick Start
52
+
53
+
**Check for ready work:**
54
+
55
+
```bash
56
+
bd ready --json
57
+
```
58
+
59
+
**Create new issues:**
60
+
61
+
```bash
62
+
bd create "Issue title" --description="Detailed context" -t bug|feature|task -p 0-4 --json
63
+
bd create "Issue title" --description="What this issue is about" -p 1 --deps discovered-from:bd-123 --json
64
+
```
65
+
66
+
**Claim and update:**
67
+
68
+
```bash
69
+
bd update <id> --claim --json
70
+
bd update bd-42 --priority 1 --json
71
+
```
72
+
73
+
**Complete work:**
74
+
75
+
```bash
76
+
bd close bd-42 --reason "Completed" --json
77
+
```
78
+
79
+
### Issue Types
80
+
81
+
- `bug` - Something broken
82
+
- `feature` - New functionality
83
+
- `task` - Work item (tests, docs, refactoring)
84
+
- `epic` - Large feature with subtasks
85
+
- `chore` - Maintenance (dependencies, tooling)
86
+
87
+
### Priorities
88
+
89
+
- `0` - Critical (security, data loss, broken builds)
90
+
- `1` - High (major features, important bugs)
91
+
- `2` - Medium (default, nice-to-have)
92
+
- `3` - Low (polish, optimization)
93
+
- `4` - Backlog (future ideas)
94
+
95
+
### Workflow for AI Agents
96
+
97
+
1. **Check ready work**: `bd ready` shows unblocked issues
98
+
2. **Claim your task atomically**: `bd update <id> --claim`
99
+
3. **Work on it**: Implement, test, document
100
+
4. **Discover new work?** Create linked issue:
101
+
- `bd create "Found bug" --description="Details about what was found" -p 1 --deps discovered-from:<parent-id>`
102
+
5. **Complete**: `bd close <id> --reason "Done"`
103
+
104
+
### Auto-Sync
105
+
106
+
bd automatically syncs with git:
107
+
108
+
- Exports to `.beads/issues.jsonl` after changes (5s debounce)
109
+
- Imports from JSONL when newer (e.g., after `git pull`)
110
+
- No manual export/import needed!
111
+
112
+
### Important Rules
113
+
114
+
- ✅ Use bd for ALL task tracking
115
+
- ✅ Always use `--json` flag for programmatic use
116
+
- ✅ Link discovered work with `discovered-from` dependencies
117
+
- ✅ Check `bd ready` before asking "what should I work on?"
118
+
- ❌ Do NOT create markdown TODO lists
119
+
- ❌ Do NOT use external issue trackers
120
+
- ❌ Do NOT duplicate tracking systems
121
+
122
+
For more details, see README.md and docs/QUICKSTART.md.
123
+
124
+
## Landing the Plane (Session Completion)
125
+
126
+
**When ending a work session**, you MUST complete ALL steps below. Work is NOT complete until `git push` succeeds.
127
+
128
+
**MANDATORY WORKFLOW:**
129
+
130
+
1. **File issues for remaining work** - Create issues for anything that needs follow-up
131
+
2. **Run quality gates** (if code changed) - Tests, linters, builds
132
+
3. **Update issue status** - Close finished work, update in-progress items
133
+
4. **PUSH TO REMOTE** - This is MANDATORY:
134
+
```bash
135
+
git pull --rebase
136
+
bd sync
137
+
git push
138
+
git status # MUST show "up to date with origin"
139
+
```
140
+
5. **Clean up** - Clear stashes, prune remote branches
141
+
6. **Verify** - All changes committed AND pushed
142
+
7. **Hand off** - Provide context for next session
143
+
144
+
**CRITICAL RULES:**
145
+
- Work is NOT complete until `git push` succeeds
146
+
- NEVER stop before pushing - that leaves work stranded locally
147
+
- NEVER say "ready to push when you are" - YOU must push
148
+
- If push fails, resolve and retry until it succeeds
149
+
150
+
<!-- END BEADS INTEGRATION -->