Why headless agents are deferred in v0.1
The credential boundary that keeps v0.1 local until Coldvio ships audited, scoped, revocable provisioning.
Keep v0.1 credentials local
The first release intentionally has no command that prints a stored bearer token. Use interactive login on a customer-controlled machine. Defer hosted/headless use until Coldvio provides an audited, revocable provisioning flow; never upload or scrape credentials.json.
Future provisioning requirements
A future hosted-agent flow must mint a separately scoped and revocable credential without exporting the local CLI token. It should default to read-only, expose ownership and expiry, and preserve a real human approval boundary for consequential tools.
Keep diagnostics safe
- Never enable shell tracing around secret injection.
- Never read or print credentials.json from an agent process.
- Redact Authorization headers and callback URLs.
- Limit response logging when CRM or message content is returned.
Do not improvise provisioning
COLDVIO_API_TOKEN is a runtime override, not a v0.1 export workflow. Do not copy the local credential into CI, invent a scraping step, or enable hosted use until the audited provisioning contract is released.