aedibase-cli

The CLI for aedibase — a scale-to-zero, Supabase-wire-compatible backend (BaaS). Zero install, drive it from your terminal or a coding agent.

# 1. mint an API token in your console (API tokens → create), then:
npx aedibase-cli login --token aedu_...

# 2. create + link an app (installs agent skills + writes AGENTS.md)
npx aedibase-cli create my-app
npx aedibase-cli link <ref> my-app

# 3. now your coding agent (Claude Code, Cursor, Codex) has the aedibase skills —
#    just tell it: "add email login and a todos table with row-level security"

link installs three agent skills into ~/.claude/skills (aedibase for app code, aedibase-cli for backend/infra, aedibase-debug for diagnosing failures) and writes an AGENTS.md with this app's endpoints and gotchas, so an agent uses the real API instead of guessing.

Commands

| | | |---|---| | login --token aedu_… | store your API token (~/.aedibase/credentials.json) | | link <ref> [name] | link this directory: .aedibase/project.json + skills + AGENTS.md | | create <name> | create an app → ref + anon/service keys | | list · get [ref] | your apps / one app's detail | | sql [ref] "<query>" | run SQL (or pipe on stdin) | | schema [ref] · types [ref] | tables/RLS/advisors · TypeScript row types | | connection [ref] | the direct Postgres connection string | | diagnose [ref] | health report: state, RLS advisors, quota | | logs [ref] [db\|rest\|auth] · sleep\|wake [ref] · delete <ref> --yes | |

[ref] defaults to the app linked in .aedibase/project.json.

Env: AEDIBASE_CONTROL_URL (default https://app.aedify.ai), AEDIBASE_TOKEN.

aedibase apps nap to 0 RAM when idle and wake on the next request (~3s cold) — use generous timeouts. Supabase-wire-compatible, so @supabase/supabase-js works against the data plane (https://db.aedify.ai/a/<ref>), except realtime.