Kibaco

    Quick Start

    Create a config in your project directory:

    kibaco init

    Kibaco infers sensible defaults from package managers, package.json, dev scripts, .env ports, common frameworks, simple backend/server files, monorepo app folders, and Compose files when it can. Inferred local hostnames include the workspace directory as a prefix, such as my-app-web.localhost, to avoid collisions across repositories. When .tool-versions pins nodejs, inferred Node commands are wrapped with asdf exec, such as asdf exec pnpm dev. .nvmrc, .node-version, and Volta Node pins are reported by kibaco dev and kibaco doctor.

    Start the environment:

    kibaco dev

    Open a project URL:

    kibaco open web

    That is the normal daily workflow.

    Override Inferred Values

    kibaco init --project web --host web.localhost --target http://localhost:3000 --cmd "pnpm dev"

    Preview inferred config without saving it:

    kibaco init --detect

    Force an interactive review:

    kibaco init --interactive

    kibaco init can detect:

    • Package managers: pnpm, npm, yarn, bun
    • Frontend frameworks: Next.js, Vite, Astro, Nuxt, Remix
    • Backend projects: Rails, Laravel, Django, Go, Rust, simple Node servers
    • Monorepos: pnpm-workspace.yaml, turbo.json, nx.json, apps/*, packages/*, services/*
    • Environment ports: .env, .env.local, .env.development
    • Compose services: images, ports, environment, volumes, dependencies, and common health checks
    • Node version pins: .tool-versions, .nvmrc, .node-version, and package.json Volta settings

    Check the Workspace

    kibaco doctor

    doctor checks the active config, proxy port, Docker availability when Docker services are configured, service references, project working directories, service status, and target reachability.