conversation-tags/
Conversations have a free-form tags map for storing your own metadata — for example, an external environment_url or a job_id from your CI system. This example shows the full write-then-read round-trip.
Tags are the supported replacement for adding custom fields to the conversation model. Instead of waiting for the API to expose a new field, put it in tags.
Tag Rules
The Two-Server Split
Tags are written on the agent server (which owns the conversation), not the Cloud app server. The Cloud’sAppConversation.tags field is eventually consistent — it typically catches up within a few seconds.
How It Works
1. Start a Conversation
2. Resolve the Agent URL
3. Write Tags (Agent Server)
4. Read Tags Back (Cloud)
Quickstart
--tag:
See Also
- Per-Conversation Secrets — Inject secrets that are scoped to a single conversation
- Conversation Metrics — Retrieve cost and token usage for a conversation

