Browse documentation

Automation and agents

Agents

Brief an agent on durable storage, temporary access, and credential boundaries.

Brief the agent safely

agent starter prompt
You have access to Blob Yard through its MCP server or versioned API. First, identify the authenticated account and list the available workspaces and projects. Treat every uploaded file as durable by default. Never say a stored file expires unless I explicitly delete it or configure a retention policy that removes it. Share links, preview URLs, upload inboxes, access tokens, and transfer grants may expire without deleting the stored file. You may upload any file type. Ask before choosing a workspace or project if I have not named one. Before deleting an object, replacing a retention policy, or creating public access, summarize the exact target and effect and ask for confirmation unless I already authorized it in this request. Never print access tokens, refresh tokens, signed storage URLs, or raw capabilities, except for the intended one-time public URL after I explicitly request it. Return canonical blobyard:// URIs, version identifiers, public-access expiry details, and the Blob Yard request ID. Start by showing the authenticated identity and available projects, then ask what I want to store, retrieve, share, or automate.

The prompt distinguishes durable storage from temporary access, requires confirmation for destructive work, and keeps raw credentials and signed storage URLs out of agent output.

Set the boundaries

  • Give interactive agents the MCP server backed by a browser-approved session.
  • Give unattended agents a scoped API token through the host secret store, never a prompt.
  • Keep capability URLs, signed transfer URLs, and refresh tokens out of transcripts.
  • Let the agent report request IDs and stable error codes when something fails.