** AI 에이전트 조정을위한 그래프 기반 문제 추적기. **

AI와 코딩은 개발자가 absurdly 생산 능력을 만듭니다. 커피는 그들을 유지. 빈은 전체 루프를 먹었다. 😀

Beans는 AI Agent를 위해 설계된 경량, 임베디드 발행 추적기입니다. 업무 전반에 걸쳐. 신뢰할 수 있는 그래프의 노드로서의 모델 문제, SQLite에 의해 백업, 와 인간과 대리인 둘 다 사용할 수 있다는 것을.

왜 콩 존재

콩은 항문 구슬, 유사한 목표의 그래프 기반 문제 추적기 : AI Agent를 구조화하는 방법을 제공합니다. 협조 일. 아이디어는 우수합니다. 실행, 그러나, 심각한 문제를 제기.

구슬과 문제

Beads는 사용자의 의도에 대해 너무 많이 가정하는 침략적인 소프트웨어입니다.

• Curl-pipe-bash installer는 ~200MB를 설치하기 위해 sudo]에 자동으로 에스컬레이터가 됩니다. 바이너리 시스템
• **Strips macOS 코드 서명 ** 및 게이트키를 우회하기 위해 AD-HOc 서명 적용 - 실제 악성 코드에 의해 사용되는 동일한 기술 -Installs 5 persistent git Hooks ([T1]], post-merge], pre-push], post-checkout, prepare-commit-msg]) 거의 모든 git 작업에 실행

🫘 Beans

Graph-based issue tracker for AI agent coordination.

Coding with AI makes developers absurdly productive. Coffee keeps them going. Beans keep the whole loop fed. ☕

Beans is a lightweight, embedded issue tracker designed for AI agents to coordinate work across tasks. It models issues as nodes in a dependency graph, backed by SQLite, with a CLI that both humans and agents can use.

$ beans create "Fix auth middleware"
task-a3f2dd1c  2025-06-15 10:42  Fix auth middleware

$ beans list
task-a3f2dd1c  2025-06-15 10:42  Fix auth middleware
task-7e2b9f01  2025-06-15 10:43  Add rate limiting

$ beans --json list
[{"id": "task-a3f2dd1c", "title": "Fix auth middleware", "status": "open", ...}]

Why Beans exists

Beans was born from analyzing beads, a graph-based issue tracker with a similar goal: giving AI agents a structured way to coordinate work. The idea is excellent. The execution, however, raised serious concerns.

The problem with beads

Beads is invasive software that assumes too much about the user’s intentions:

• Curl-pipe-bash installer that silently escalates to sudo to install a ~200MB binary system-wide
• Strips macOS code signatures and applies ad-hoc signatures to bypass Gatekeeper — the same technique used by actual malware
• Installs 5 persistent git hooks (pre-commit, post-merge, pre-push, post-checkout, prepare-commit-msg) that run on nearly every git operation
• Runs a background database daemon (Dolt SQL server) that binds to TCP ports 3307/3308 — a MySQL-protocol server running on your machine
• Silently modifies commit messages by appending metadata trailers without asking
• Auto-pushes data to remote servers every 5 minutes
• Fingerprints your machine with unique UUIDs for the repo, clone, and project
• Injects system prompts into AI agent configuration files (e.g., .claude/settings.local.json) to force agents to use the tool
• Includes a “stealth mode” that hides its presence from collaborators
• Ships with telemetry that records every command and all arguments, including who ran them

The core data model is a 50+ field struct covering everything from agent heartbeats to ephemeral “wisps.” It’s not a simple tool — it’s a complex system that assumes you want all of it.

What beans does differently

Beans keeps the good idea — a dependency graph for AI agent coordination — and throws away everything else: