Dibbla CLI

The

dibbla

CLI scaffolds projects and manages applications, databases, secrets, and workflows on the Dibbla platform. Deployed apps are available at

https://<alias>.dibbla.com

Commands at a glance

Area	Commands
Feedback	`feedback <message>` , `feedback list` , `feedback delete <id>`
Deploy	`deploy [path] [--alias name]` — deploy from directory
Apps	`apps list` , `apps update <alias>` , `apps delete <alias>`
Db	`db list` , `db create` , `db delete` , `db dump` , `db restore` , `db connect`
Secrets	`secrets list` , `secrets set` , `secrets get` , `secrets delete` (global or `-d <alias>` )
Workflows	`workflows list` , `get` , `create` , `update` , `delete` , `validate` , `execute` , `url` , `api-docs`
Nodes	`nodes add <wf>` , `nodes remove <wf> <id>`
Edges	`edges add <wf> "<edge>"` , `edges remove` , `edges list`
Inputs	`inputs set <wf> <node> <input> <value>`
Tools	`tools add <wf> <agent> <tool>` , `tools remove`
Revisions	`revisions list <wf>` , `revisions create` , `revisions restore`
Functions	`functions list` , `functions get <server> <name>`

Agent guidelines

Interactive prompts: The following commands prompt for confirmation and will block if run non-interactively. Always pass

--yes

(or

-y

) when running these as an agent:

```
dibbla apps delete <alias> --yes
```
```
dibbla db delete <name> --yes
```
```
dibbla secrets delete <name> --yes
```
```
dibbla workflows delete <name> --yes
```
```
dibbla nodes remove <wf> <id> --yes
```
```
dibbla feedback delete <id> --yes
```

Deploying an app for the first time:

Check if the app already exists:
```
dibbla apps list
```
If it does not exist, deploy with all required environment variables included in the deploy command — there is no app to attach them to yet:
bash
```
dibbla deploy . --alias my-app -e DATABASE_URL=postgres://... -e API_KEY=secret -e NODE_ENV=production
```
If it already exists, use
```
--update
```
for a zero-downtime rolling update:
bash
```
dibbla deploy . --alias my-app --update
```
To change env vars on an existing app, use
```
apps update
```
instead:
bash
```
dibbla apps update my-app -e NEW_VAR=value
```

Key rules:

```
--force
```
causes downtime (tears down and redeploys). Prefer
```
--update
```
for existing apps.
```
--force
```
and
```
--update
```
are mutually exclusive.
Environment variables set via
```
deploy -e
```
or
```
apps update -e
```
persist across updates — you only need to pass them once.
Use
```
--quiet
```
/
```
-q
```
on
```
db list
```
,
```
db delete
```
,
```
db connect
```
for machine-readable output in scripts.
```
db create --deployment <alias>
```
scopes the database and its auto-created
```
DATABASE_URL
```
secret to a specific deployment.
```
db connect
```
prints a psql-compatible connection string via the Dibbla database proxy. Use
```
-q
```
for scripting:
```
psql $(dibbla db connect mydb -q)
```
.

Pre-deploy guardrails: Before calling

dibbla deploy

, you MUST complete the pre-deploy checklist and present findings to the user. Always wait for explicit user confirmation before deploying or fixing issues — never deploy autonomously. See guardrails.md for the full checklist.

Additional resources

Full command and flag reference: see reference.md for usage, arguments, and all flags.
Usage examples: see examples.md for copy-paste examples and scripting patterns.
Pre-deploy guardrails: see guardrails.md for the mandatory pre-deploy checklist.

When suggesting or generating

dibbla

commands, use the reference for exact syntax and the examples for typical workflows.

dibbla

NPX Install

Tags

SKILL.md Content

Dibbla CLI

Commands at a glance

Agent guidelines

Additional resources