Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.insforge.dev/llms.txt

Use this file to discover all available pages before exploring further.

The @insforge/cli is the interface a coding agent uses to operate your backend. Where a human reaches for the dashboard, the agent reaches for the terminal: it runs a command, reads the output, and decides what to do next. Every command speaks --json, so the agent works from structured data instead of scraping a screen.
Run the CLI with npx @insforge/cli. Do not install it globally, so the agent always uses the version pinned to the project.

​
Why a CLI for agents

A dashboard is built for a human pointer; a CLI is built for anything that can write text. Pass --json to any command and the agent gets a structured result it can parse; pass --yes and it runs without stopping for a confirmation prompt. Schema, auth config, storage, functions, deploys, branches, and diagnostics are all subcommands of the same tool, so there is one surface to learn instead of a dashboard to navigate. It runs in any terminal, any editor, or CI, with no integration to set up. And after a change, the agent can run npx @insforge/cli diagnose and read back exactly what broke.

​
Command surface

AreaCommands
Auth & contextlogin, logout, whoami, current, list
Projectcreate, link
Schemadb migrations new, db migrations up, db migrations list
Config as codeconfig plan, config apply, config export
Branchingbranch create, branch merge, branch reset, branch delete
Buildfunctions, storage, deployments, secrets, schedules, ai
Diagnosediagnose, diagnose advisor, diagnose db, diagnose logs, metadata
Run npx @insforge/cli help <command> for the flags on any of these.

​
A typical agent run

# connect
npx @insforge/cli login
npx @insforge/cli link

# read current state
npx @insforge/cli --json metadata

# change schema, safely
npx @insforge/cli db migrations new add-orders-table
npx @insforge/cli db migrations up --all

# check the result
npx @insforge/cli diagnose --json

​
Let the agent interpret the output

Diagnostics ships an AI flag so the agent can hand its own backend data to a model and get back an explanation: 
npx @insforge/cli diagnose --ai "why are auth requests failing after the last migration?"
This pairs the raw signals (advisor findings, DB health, error logs) with a plain-language read, which is what turns “here is a stack trace” into “here is the fix.” See Diagnostics & advisor.

​
Next steps