Create a named key
Use one key per device or agent. hdoc shows its secret once; save it locally as HDOC_API_KEY, never in a repo or shared config.
Connect your coding agent to hdoc in four safe steps.
Keep one secret in your local environment, give the agent a small operating context, then prove the connection with a read before it publishes anything.
Fastest path
Paste one prompt into Codex or Claude.
The agent fetches the current setup contract before changing local configuration. Your raw key stays out of the prompt.
Fetch https://hdoc.docenty.ai/agent-setup/prompt.md and follow it to connect hdoc. Ask me for an API key only when needed, keep it in HDOC_API_KEY, and verify with a read-only search before publishing anything.Choose your agent
export HDOC_API_KEY='hdoc_sk_...'
codex mcp add hdoc --url https://hdoc.docenty.ai/api/mcp --bearer-token-env-var HDOC_API_KEY
codex mcp listInstall the operating context
Give the agent hdoc's compact skill. It explains when to publish, when to create a draft, and the approval boundary.
Fetch https://hdoc.docenty.ai/skill/hdoc and install it as the hdoc skill for this agent.Verify with a read
Run this first. It confirms access without creating, updating, or approving any shared content.
Search my approved hdoc content for "sales deck" and return the best reusable package with its provenance. Do not create or change anything.What this connection can do
The agent can search content this key is authorized to access and create a fork or adaptation as a draft. It cannot silently replace an approved shared version; you review every agent-created version in hdoc.