bacio.io

What it is

bacio is a local-first kanban tool built for the “Agent era”: it is simultaneously a CLI, a TUI, and a syncable Git data repository. By default, data is stored locally at ~/.bacio/db.sqlite. Developers can use bacio tui in the terminal to view boards, features, docs, and history, while AI Agents can use its stable JSON CLI to create issues, plan features, write documentation, and read audit history.

Core capabilities

Its most distinctive design choice is being Agent-friendly. All mutation commands support --json and can read input inline, from stdin, or from a file. At runtime, bacio schema can output a draft 2020-12 JSON Schema. Every mutation supports --dry-run, allowing an Agent to validate changes before executing them. bacio install-skill writes the built-in SKILL.md to .claude/skills/bacio/, where it can be read by Claude Code and Codex.

The TUI is a fully keyboard-driven kanban interface with four tabs: Board, Features, Docs, and History. It suits terminal users who do not want to switch to a browser. For sync, bacio sync maps the local SQLite database to Markdown + YAML, then uses a standard Git remote to pull, import, export, commit, and push. It can work with GitHub, GitLab, Gitea, or a self-hosted Git server.

Pricing and deployment

The crawled text does not provide any pricing, paid edition, or commercial support information. The deployment model is local-oriented: a single user can rely on SQLite only, while teams can configure a separate sync repo. The text also mentions bacio api and an entry point to “Run the API server,” but does not elaborate on the API Server details.

Pros and cons

Its strengths are that it is local-first, works offline, and keeps data diffable, blameable, and revertible through Git. Its audit log records the actor and operation for every mutation. The CLI rules are strict and well suited to automation and LLM calls. The downsides are that sync is not real-time collaboration, conflict handling still follows the Git workflow, the TUI is roughly designed for a 130-column terminal, making narrow-screen use less ideal, and it has a higher barrier for non-terminal and non-Git users.

Who it’s for and access from China

bacio is a good fit for developer teams using Claude Code or Codex, as well as engineers who want to keep tasks, documentation, and decision records inside a Git/Markdown workflow. The source text does not explain access conditions from China. If it depends on GitHub, Homebrew, or external model tools, real-world network and payment experience may be affected by those services. If you need a mature SaaS product or real-time collaboration, you may want to compare it with Linear, Jira, GitHub Projects, Plane, Trello, and similar tools.