Skip to content

CLI: Dev

Generated from deedglass help --json (CLI 0.1.0-dev). Global flags and exit codes are on the CLI reference page.

Load demo data into a dev database.

Terminal window
deedglass dev seed [--demo [--keys-file <path>] [--approver <email>]] [--json]
Flag Type Default What it does
--approver string with –demo: add this email as an admin of the demo org, so approval emails reach it (S22)
--demo bool load the Acme demo org, agents, keys and policy instead (S15)
--keys-file string examples/demo/.demo-keys with –demo: where the agents’ keys are written (0600)

Add --json for machine-readable output.

Seal realistic fake actions (dev only).

Terminal window
deedglass dev fake-action [--n 20] [--seed 42] [--kinds allow,deny,…] [--agents 3] [--batch 1] [--pace 0s] [--org-slug demo] [--quiet] [--json]
Flag Type Default What it does
--agents int 3 how many demo agents (1 to 8)
--batch int 1 actions per transaction (500 for bulk seeding)
--kinds string comma list: allow, deny, mismatch, unverifiable, failed, pending, amend
--n int 20 how many actions
--org-slug string demo the demo org’s slug (created when missing); –org picks an existing org instead
--pace duration 0s pause between actions for live demos (200ms)
--quiet bool print only the final line
--seed int 42 the same seed gives the same tools, arguments, latencies and verdicts

Add --json for machine-readable output.

Simulate a week of agent traffic (dev only).

Terminal window
deedglass dev simulate [--scenario examples/sim/acme.yaml] [--days 7] [--end now|-2d] [--seed 7] [--org org_… | --org-slug acme-sim] [--append] [--pace 0s] [--quiet] [--json]
Flag Type Default What it does
--append bool add days to an existing simulated org instead of creating a fresh one
--days int 7 how many days to simulate (1 to 90)
--end string now when the window ends: now, -2d, -12h, or an RFC 3339 time (truncated to the org-local hour)
--org string with –append: the simulated org (org_…)
--org-slug string the fresh org’s slug (default the scenario’s), or with –append the org to add to
--pace duration 0s pause between actions (live demos, like 200ms)
--quiet bool print only the result line
--scenario string the scenario file (default: the embedded examples/sim/acme.yaml)
--seed int 7 the same seed and scenario give the same tools, arguments, times, outcomes and approval waits

Add --json for machine-readable output.

Run a scripted agent.

Terminal window
deedglass dev agent-script <script.yaml> [--step] [--live] [--only <scene>] [--keys-file examples/demo/.demo-keys] [--root .] [--var name=value] [--json]

Add --json for machine-readable output.

Preview emails in the browser.

Terminal window
deedglass dev mail-preview login|invite|approval|approval-foureyes [--out /tmp/login.html] [--json]
Flag Type Default What it does
--out string write the HTML to this file (default: a temporary file)

Add --json for machine-readable output.

Sign an intent with a local key.

Terminal window
deedglass dev sign-intent --key <pem> --tool stripe.refund --args '{…}' [--org org_… --agent agt_…] [--obo …] [--session …] [--ttl 60s] [--explain] [--json]
Flag Type Default What it does
--agent string the agent’s id (agt_…); from whoami when an API key is set
--args string the exact JSON arguments, like ‘{“amount”:1200}’
--explain bool show every step: args, digest, intent, hash, header
--key string the PKCS#8 PEM private key keygen wrote
--nonce string use this nonce, 32 lowercase hex (tests and vectors)
--now string sign as of this RFC 3339 time (tests and vectors)
--obo string sign Deedglass-On-Behalf-Of: the person the agent serves
--session string sign Deedglass-Session: the conversation or run
--tool string the connector.tool name, like stripe.refund
--ttl duration 1m0s how long the intent is valid, at most 5m

Add --json for machine-readable output.

Create Stripe sandbox fixtures.

Terminal window
deedglass dev stripe-fixtures [--from-env STRIPE_TEST_KEY] [--connector stripe] [--out examples/demo/.stripe-fixtures.json] [--json]
Flag Type Default What it does
--connector string stripe the Stripe connector’s name (for messages)
--from-env string STRIPE_TEST_KEY the environment variable holding a sandbox key (rk_test_ or sk_test_)
--out string examples/demo/.stripe-fixtures.json where to write the ids (mode 0600)

Add --json for machine-readable output.