Developer loop
Overview
Build and debug engine and app scripts locally against real workspace files, exactly like a platform run.
The developer loop lets you write engine/app scripts locally but read and write real workspace
files — exactly like a platform run. The CLI mints a scoped token, generates the platform's
execution context, and injects it so the verentis-engine-sdk
talks to the actual workspace.
The fast path
From a project with an engine.yaml (whose spec.permissions declares the scopes it needs):
cd my-engine-project
verentis dev run transform.py --workspace <id> --params '{"message":"hi"}'
dev run:
Mints a scoped token
Scopes come from ./engine.yaml spec.permissions (or --scopes), so engine.files / engine.http
in your script hit the real workspace with exactly those permissions.
Generates the execution context
It writes .verentis/context.json (mode 600 — it contains a short-lived token) describing the run
the way the platform would.
Runs your script
The SDK auto-loads that context, so your local process behaves like a platform execution. The file is
removed after the run unless you pass --keep-context.
Git-ignore .verentis/
.verentis/context.json holds a short-lived scoped token. Add .verentis/ to your .gitignore.