Scriptum CLI Guide
Last validated: 2026-05-14
This CLI guide is split by command domain and uses Dodil CLI plugin mode in examples:
dodil scriptum ...Read By Domain
- Install assumptions, login, global flags, config precedence, environment variables.
- Script lifecycle commands for authoring, compile/test loops, publishing, rollback.
- Thread creation, watch/poll behavior, result retrieval, step-level inspection.
- Tenant env management, tool list, health checks, and troubleshooting commands.
- Missing command coverage and direct gRPC/HTTP alternatives.
Command Coverage Snapshot
| Area | API support | CLI support | Notes |
|---|---|---|---|
| Script CRUD + draft + version lifecycle | Yes | Yes | Core authoring path is complete |
| Thread create/get/list/watch/result/steps | Yes | Yes | Run/observe/retrieve flows are covered |
| Resume thread | Yes | No | Use gRPC/HTTP workaround |
| Script env overlay APIs | Yes | No | Use gRPC/HTTP workaround |
| Templates list/get | Yes | No | Use gRPC/HTTP workaround |
| Get script code | Yes | No | Use gRPC/HTTP workaround |
| Tool register/get | No | No | API unimplemented |
| Cancel thread | No | No | API unimplemented |
| Artifact list | No | No | API unimplemented |
Recommended Use Pattern
- Use
dodil scriptumfor all covered day-to-day operations. - For missing but implemented RPCs, use
grpcurlwrappers. - Use JSON output (
-o json) for automation and CI parsing. - Run
dodil scriptum doctorwhen auth or endpoint behavior is unclear.