Development

Run:

kibaco dev
kibaco dev web
kibaco dev --select
kibaco dev --verbose
kibaco dev web --watch-health

Kibaco will:

  1. Find the Kibaco workspace config for the current directory
  2. Start services referenced by the selected projects
  3. Wait for configured health checks
  4. Start SSH tunnels for remote projects
  5. Start local project commands
  6. Start or reuse the local proxy
  7. Print the URLs for each project

With no project names, kibaco dev starts all configured projects. Use project names or --select when you only want part of the workspace. Use --verbose when you want project output streamed inline.

For a project with "remote": "devbox:3004", Kibaco opens an SSH local forward and skips the local project command. The SSH host must already work with your normal ssh devbox command.

Kibaco captures each project process log without streaming it to the terminal by default.

~/.kibaco/logs/{workspace}/{project}.log
~/.kibaco/logs/{workspace}/{project}.jsonl

The text log is easy to read in a terminal. The JSONL log keeps time, project, stream, and line fields so tools and AI assistants can read only the project and stream they need.

Use --watch-health when a dev server can get stuck after builds. Kibaco probes the selected project's HTTP health URL every 60 seconds and restarts the project after 3 consecutive 500-level responses or connection failures. Configure an HTTP project.healthCheck.url for a dedicated endpoint such as /api/health, or Kibaco will probe the project target URL.

kibaco logs
kibaco logs web
kibaco logs web --follow
kibaco logs --all --tail 200
kibaco logs web --jsonl
kibaco logs mysql

Show the configured local URLs again after startup:

kibaco urls

Restart a project without stopping the proxy:

kibaco restart web
kibaco restart --all

kibaco restart asks the running kibaco dev process to restart the project, so logs and proxy routing remain under the same dev session.

Stopping

Press Ctrl+C to stop the project processes and the proxy started by Kibaco.

Services are left running so databases and external local stacks stay available during development. Stop them explicitly with:

kibaco services down