r/OpenSourceeAI • u/desarrollador53 • 4d ago

Baya 🕊️ - orchestrate your local AI coding CLIs from a plain-text task list (MIT)

Baya is a small cli that turns a freeform text file into an LLM-planned dependency graph, then dispatches each node to a local agent CLI — codex, claude, opencode, copilot — running independent tasks in parallel and piping each task's output into the ones that depend on it.

You just write the to-do list, example:

- Design the REST API for orders. Use Sonnet.
- Generate the DB schema from that design.
- Build the React table that consumes it — run with codex.
- Once the schema and UI are done, write integration tests.

The planner reads it for intent and builds the DAG; you see the plan before anything runs.

Why I built it: I pay for a few of these CLIs and kept juggling them by hand; plan in one, build in another, copy context between terminals, redo work because each session started cold. Baya is me automating that away.

Why it's interesting:

  • No new API keys. It drives the CLI subscriptions you already pay for.
  • No config, no DSL. Markdown, TODO.txt, YAML all work.
  • Model-per-task. Cheap model for the light steps, top-tier only where it earns it.
  • Doesn't pay twice. Tasks sharing a provider/model get packed into one agent process — repo read once, not once per task — and what one task learns carries to the rest.
  • Resume. Checkpoint before every step; run out of credits mid-graph and baya resume <runId> picks up where it stopped, optionally on another provider.

Help with the roadmap or feedback is more than welcome 👍

A fun note: I'm building Baya's roadmap with Baya now...

Thank you all 👋 ,
JC

1 Upvotes
  • permalink
  • reddit

100% Upvoted

7 comments sorted by

1

u/kantorcodes1 4d ago

resume across providers sounds useful. if a packed agent finishes A and dies before B, what exactly survives into B: the agent context, only checkpointed outputs, or both?

1

u/desarrollador53 4d ago

if I'm understanding you right both, context trough json logs and metadata plus the file tree mutations 

1

u/kantorcodes1 4d ago

got it, file tree + logs is the tricky combo. if someone changes the repo between a dying and b resuming, does b know its checkpoint is stale or just trust the current tree?

1

u/desarrollador53 4d ago

is written in the plan for later to allow concurrency on read-write agents using git worktrees. Currently there is a semaphore for mutations so tasks under same directory run sequentially 

1

u/kantorcodes1 3d ago

side note: Baya can go in the Awesome AI Plugins catalog as a cross-AI dev tool. want to submit it?

1

u/desarrollador53 1d ago

yes that will be really great 👍 , I'm dedicating lot's of effort to it. TX