Two-terminal debugging workflow
Runs an AI assistant in the terminal while a second command starts your application under debugging. This keeps the debugging conversation close to the live process.
OpenBug CLI
OpenBug CLI is an AI-powered command-line debugging tool for live logs and local code search, built for real-time terminal debugging across services.
Overview
OpenBug CLI is a command-line tool for debugging running applications with AI assistance. It combines a terminal assistant, live log capture, and local codebase search so you can investigate issues while the app is actually executing.
The workflow is centered on `debug`: one terminal starts the assistant, and another runs your app or service through `debug <command>`. The README says this can help with single services or multiple services connected to the same local cluster, while keeping code access local and streaming logs only when needed for analysis.
Core features
Automatic log capture
Automatically captures logs from the running service and makes them available to the assistant so answers are based on runtime behavior instead of static analysis alone.
Natural-language code search
Searches the local codebase in natural language, allowing questions such as where a webhook or token validation path is handled without manual grep.
Multi-service coordination
Connects multiple running services to the same local cluster, which lets the assistant correlate logs and code across a larger stack.
Terminal and browser interfaces
Provides a browser-based `studio` mode and a terminal UI with shortcuts for switching views, reconnecting, and managing the chat/log display.
Project configuration
Supports first-time project setup that creates `openbug.yaml` and registers the service with the local cluster automatically.
Where it fits
Debug a live app
Run a service with `debug <command>` while the assistant watches logs and answers questions about what the application is doing at runtime.
Investigate a multi-service stack
Connect backend and frontend services to the same cluster so the assistant can trace failures across logs from multiple terminals.
Orient yourself in a codebase
Ask natural-language questions about unfamiliar code, such as where a feature or validation path is implemented, and let the assistant search locally.
Switch to a visual debugging view
Use the browser `studio` view when you want a different debugging interface than the terminal and need to inspect chat or logs visually.
Standardize a project setup
Set up a new project with the first-run prompts and generated `openbug.yaml` so the same configuration is reused on later runs.
Pros and Cons
Pros
- Combines command execution, logs, and AI guidance in one terminal-oriented workflow.
- Uses runtime logs and local code search, which makes answers more context-aware than static code assistance alone.
- Supports debugging across multiple services connected to the same cluster.
- Includes both terminal and browser interfaces, plus shortcuts for switching views and reconnecting.
Cons
- The project is marked beta and actively developed, so behavior and workflows may still change.
- It requires a specific setup with a local cluster, an API key, and Node.js 20+.
- The README notes that code is accessed locally and only selected snippets are sent, which may be a constraint for teams that want a fully offline workflow.
FAQ
How do I set it up for a new project?
OpenBug CLI starts an AI assistant in one terminal and runs your application command in another. On first use in a directory, it prompts for a project description and creates an `openbug.yaml` configuration file.
What does OpenBug CLI help with?
The README says OpenBug can capture logs automatically, search your codebase in natural language, and chat with an AI that understands the running system. It is designed for debugging live applications rather than static code review.
Can it work across multiple services?
The CLI supports workflows where multiple services are running in separate terminals and connect to the same local cluster, so the AI can inspect logs across services and search code in more than one repository.
What gets sent to the server?
The README states that your code stays local and is accessed locally, while only specific snippets queried by the AI are sent to the server. Logs are streamed only when needed to answer a question.
Is it production-ready?
OpenBug CLI is in beta and actively developed. The source also lists Node.js 20+ and a compatible package manager as requirements, so users should expect an evolving tool with a defined runtime setup.
Quick Facts
- Category
- Developer Tool
- Primary interface
- Terminal CLI with optional browser studio
- Package name
- @openbug/cli
- Command
- `debug`
- Requirements
- Node.js 20+ plus npm, yarn, or bun
- Source domain
- github.com
OpenBug CLI Alternatives
AakarDev AI
AakarDev AI helps teams manage AI provider access, project setup, logs, and analytics in one dashboard. BYOK support included.
ByteAsk
ByteAsk is a terminal-first AI coding agent for C and C++ that edits repos and verifies changes with compilers, debuggers, sanitizers, and tests.
PromptScout
PromptScout tracks how ChatGPT, Gemini, Google AI Overviews, and Perplexity mention your brand or competitors, with source analysis and website audits.
CreateOS Sandbox
CreateOS Sandbox is an isolated compute environment for running code and agent workloads in Firecracker micro-VMs with private networking and SDK, CLI, or MCP control.
Sleek Analytics
Sleek Analytics is a privacy-friendly web analytics tool with real-time visitor tracking, Core Web Vitals, and revenue attribution.
hob
hob is an independent workspace for coding agents, with local control over sessions, terminals, history, routing, and follow-up work.