Go CLI and library for the full Cloudflare developer platform (R2, Workers, KV, DNS, D1, and more). Includes a desktop daemon with HTTP+SSE server for the Tauri-based desktop app.
Cosmoflare exhibits significant definition quality gaps. Tool names lack clear verb-noun structure (e.g., 'apply' is ambiguous; 'apply workers' mixes verb+noun+object). Descriptions are present but generic, most lack actionable context for LLM selection. Critical issue: input schemas are inferred from parameter lists but NOT visible in source code (only parameter names and types shown, no explicit JSON Schema registration). Output schemas are completely undocumented. Error handling guidance is absent. The 'apply' tool family conflates multiple concerns (create, update, delete) without clear separation. No pagination, no structured output documentation, no recovery guidance.
Returns a list of local config profiles (AccountProfile objects). An account is a local config profile.
Apply local config changes to live Cloudflare state. Reconcile your local .cosmoflare.yaml against live Cloudflare state and apply the required changes to make live match config.
Apply DNS record config changes to live state. Creates, updates, and deletes records to match the config. Requires dns.zone_id to be set in .cosmoflare.yaml.
Apply KV namespace config changes to live state. Creates namespaces that exist in config but not in Cloudflare, and deletes namespaces that exist in Cloudflare but not in config.
Apply R2 bucket config changes to live state. Creates buckets that exist in config but not in Cloudflare, and deletes buckets that exist in Cloudflare but not in config.
Apply Workers config changes to live state. Creates workers that exist in config but are not deployed, and deletes workers that are deployed but not in config.
Input schemas not visible in source code. Parameter lists shown but no explicit JSON Schema registration or validation rules documented. Cannot verify schema completeness.
Tool naming lacks clear verb-noun structure. 'apply' is ambiguous (apply what?). 'apply workers', 'apply dns' mix verb+object without clear action. Should be 'deploy_workers', 'sync_dns_records', 'reconcile_kv_namespaces'.
Output schemas completely undocumented. No description of what 'apply' returns, what 'metrics' snapshot contains, or what 'accounts' list structure is. LLMs cannot plan downstream tool calls.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 43 | 2026-07-28+ | v2 |
Reports the two-tier health model: systems_online is always true (the daemon process is up and answering), cloudflare_online reflects the most recent Cloudflare API call outcome.
Returns a MetricsSnapshot containing one poll of account state. Sources that fail leave their field unset and carry the error message in Errors — a partial snapshot publishes instead of no snapshot.
No error handling guidance. Descriptions do not explain what errors can occur, whether they are retryable, or what the LLM should do next. E.g., 'apply' with dry-run=true could fail if zone_id is missing, but no recovery path is documented.
Destructive operations (apply with delete-unmanaged=true, apply workers/dns/kv/r2) lack confirmation or dry-run enforcement. No pattern to prevent accidental data loss.