No description
211e503409
## Design Decision Per bd (bead) system design, a task should have only ONE agent archetype assigned at a time. This provides clear ownership and simpler mental model. ## What Changed When assigning a new archetype: 1. Remove any existing agent: labels first (DELETE API) 2. Then add the new agent: label (POST API) 3. Optimistic UI updates to match ## Why This Makes Sense - Clear ownership: 'Who's working on this?' - Simpler coordination between tasks - Matches how bd/agent orchestration is intended to work - Reassigning is still possible (just click a different archetype) ## UI Behavior - If task has 'coder' assigned, clicking 'architect' will: 1. Remove 'coder' label 2. Add 'architect' label - Dropdown shows 'Assigned' badge on current archetype - X button still available to unassign completely ## Test Coverage Added graph-node-single-archetype.test.tsx with 5 tests: - Removes existing labels before adding new - Calls DELETE before POST - Only allows one archetype per task - Preserves non-agent labels - Returns early if same archetype clicked |
||
|---|---|---|
| .agent/skills/shadcn-ui | ||
| .agents/skills | ||
| .augment/skills/shadcn-ui | ||
| .beadboard/agent/runtime | ||
| .beads | ||
| .claude/skills/shadcn-ui | ||
| .cline/skills/shadcn-ui | ||
| .openhands/skills/shadcn-ui | ||
| assets | ||
| components/ui | ||
| docs | ||
| lib | ||
| out | ||
| public | ||
| scripts | ||
| skills | ||
| src | ||
| tests | ||
| tools | ||
| .eslintrc.json | ||
| .gitattributes | ||
| .gitignore | ||
| agent-help.txt | ||
| AGENTS.md | ||
| bb.ps1 | ||
| components.json | ||
| epic-help.txt | ||
| epic.txt | ||
| eslint-report.json | ||
| eslint.config.mjs | ||
| help.txt | ||
| image-1.png | ||
| image.png | ||
| label-help.txt | ||
| LICENSE | ||
| next-env.d.ts | ||
| next.config.ts | ||
| NEXT_SESSION_PROMPT.md | ||
| package-lock.json | ||
| package.json | ||
| postcss.config.js | ||
| README.md | ||
| remotion.config.ts | ||
| sse-output.txt | ||
| state-help.txt | ||
| tailwind.config.ts | ||
| task1.txt | ||
| task2.txt | ||
| task3.txt | ||
| test-output.txt | ||
| test-output2.txt | ||
| test-sse.mjs | ||
| test-watcher.ts | ||
| test2.txt | ||
| tsconfig.json | ||
BeadBoard
The Windows-native Control Center for Beads.
BeadBoard is a high-performance local dashboard for managing your software development tasks. Built on the Beads protocol, it provides a unified, visualization-rich interface over your distributed project landscape.
🚀 Why BeadBoard?
Most task managers are siloes. BeadBoard is a lens over your source code.
- Source of Truth: Reads directly from
.beads/issues.jsonlin your repo. No database sync skew. - Windows Optimized: Built from the ground up to handle Windows paths, drive letters, and filesystem performance.
- Zero Latency: Optimistic UI updates make interactions feel instant.
✨ Core Features
1. Multi-Project Registry & Scanner
Stop context switching between repos.
- Project Registry: Persist your favorite project roots for one-click access.
- Auto-Discovery: Built-in filesystem scanner finds Bead-enabled projects across your drives.
- Aggregate Mode: View tasks from all registered projects in a single unified board.
2. Interactive Kanban Dashboard (/)
Manage your flow state.
- Live Updates: Boards refresh automatically when the underlying JSONL files change (e.g., via CLI).
- Progressive Disclosure: Task details, metadata, and relations are tucked away until you need them.
- Smart Filtering: Filter by priority, assignee, status, or full-text search across thousands of beads.
3. Dependency Graph Explorer (/graph)
Understand the "Why" and "What's Next".
- Epic-Centric Layout: Automatically groups tasks by Epic for logical clustering.
- True DAG Visualization: Uses Dagre layout engine to enforce a strict Left-to-Right dependency flow.
- Left: Incoming Blockers
- Center: Focus Task
- Right: Unlocks / Downstream
- Focus Mode: Minimizable dependency strip and deep-linking support for sharing exact views.
- Smart Metadata: See bead counts, priorities, and status health at a glance.
🛠️ Stack
- Framework: Next.js 15 (App Router)
- UI Engine: React 19 + Framer Motion
- Styling: Tailwind CSS + Custom Design System
- Type Safety: Strict TypeScript
⚡ Quick Start
- Install:
npm install - Run:
npm run dev - Explore: Open
http://localhost:3000
🤝 Contribution
- Typecheck:
npm run typecheck - Test:
npm run test