HOST · Adapter
host-cloudflare
via Cloudflare Pages
Deploy + manage projects on Cloudflare Pages. Git-source mode.
@openagentry/adapter-host-cloudflare npm → — · Install
Use it
# Install
$ npm install @openagentry/adapter-host-cloudflare
# Or in a workspace registered with the CLI
$ npx agentry init @openagentry/adapter-host-cloudflare — · Default export
Pattern: lazy
The default export is always a frozen HOSTAdapter
with static category + id. Methods read env on
first call and cache the underlying instance. Missing config produces an
AgentryError at the use-site, not at import.
import default_ from '@openagentry/adapter-host-cloudflare';
// → hostAdapter — category: 'host', id: 'host-cloudflare' — · Environment
Configuration
| Variable | Notes |
|---|---|
| CLOUDFLARE_API_TOKEN | Required. |
| CLOUDFLARE_ACCOUNT_ID | Optional. |
— · Reported capabilities
What the manifest says
agentry capabilities --json reports these flags from
the package's openagentry.capabilities manifest block.
- deployMode
- git-source
- rollbackMode
- promote
- logsTail
- true
- stateExport
- true
— · Failure modes
Error codes
7 stable codes this adapter throws. Each has a one-line resolution.
-
E_CF_AUTHCloudflare API token / account ID missing or rejected. -
E_CF_NOT_FOUNDCloudflare project, deployment, or domain not found. -
E_CF_HTTPCloudflare returned a non-OK HTTP status. -
E_CF_NETWORKNetwork failure reaching Cloudflare. -
E_CF_RATE_LIMITEDCloudflare API rate limit reached. -
E_CF_PAGES_APICloudflare Pages-specific API error. -
E_CF_SCHEMAInput failed Zod validation.