System Information

ralph-tui: 0.6.0
runtime: bun 1.3.6
os: Linux 6.6.87.2-microsoft-standard-WSL2 (x86_64)
agent: claude v2.1.20
tracker: beads
beads: bd v0.49.1
global-config: no
project-config: no

Steps to reproduce

1. Create an epic in beads with 100+ tasks
2. Run ralph-tui run --tracker beads --epic <epic-id>
3. Observe that only 50 tasks are loaded

Relevant logs / terminal output

# ralph-tui shows only 50 tasks, all marked as completed
Session: abc123
Agent: claude
Tracker: beads
Epic: boilerplate-snw
[INFO] Ralph started. Total tasks: 50

# But beads has 127 tasks (44 open, 83 closed)
$ bd list --parent boilerplate-snw --limit 0 --all | wc -l
127

$ bd list --parent boilerplate-snw --status open | wc -l
44

Configuration (if relevant)

# Attempted workaround - set default limit to 0
$ bd config set list.default-limit 0

# Config is stored but not respected without explicit --limit flag
$ bd config get list.default-limit
0

# Without --limit flag, still returns ~50 results
$ bd list --parent boilerplate-snw --all | wc -l
52

# With explicit --limit 0, returns all results
$ bd list --parent boilerplate-snw --all --limit 0 | wc -l
127

Additional context

The beads CLI has a default limit of 50 results (-n, --limit int: Limit results (default 50, use 0 for unlimited)).

When ralph-tui's beads tracker fetches tasks, it appears to use the default limit, causing large epics to be truncated. The 44 open tasks in my epic were beyond the 50-task limit and not visible to ralph-tui.

Proposed solutions:

1. Pass --limit 0 when the beads tracker calls bd list
2. Add a --beads-limit option to ralph-tui run
3. Respect the beads list.default-limit config in the tracker plugin