Chat with the Roboflow AI agent.
Use this tool for:
- **Roboflow Q&A** — the agent has the full Roboflow
documentation indexed (SDKs, REST API, deployment options,
training, batch processing, Universe, blocks, pricing,
etc.). Ask it anything about how Roboflow works.
- **Advanced workflow building** — workflows complex enough
that direct block composition via ``workflow_blocks_*`` is
impractical. The agent knows every block and connection
pattern.
- **Solution planning** — pass ``mode="plan"`` and the user's
problem; the agent uses a stronger planning model to scope
a CV solution end-to-end before any building happens.
For straightforward workflows you can construct yourself, the
direct ``workflow_*`` tools are fine — you don't have to route
every workflow through the agent.
## Conversation flow
The agent runs a multi-step conversation. It may ask
clarifying questions, recommend a model, or (in plan mode)
produce a plan for confirmation. Pass the returned
``conversation_id`` back on follow-up calls to keep context.
Use ``agent_conversations_list`` and ``agent_conversation_get``
to find and resume past conversations.
## CRITICAL: the agent NEVER publishes workflows
Every workflow the agent creates or edits is saved as a
**draft**. The published version that callers using the
workflow by id will hit is unchanged until you explicitly
publish.
To make agent edits live, call ``agent_workflow_publish`` with
the workflow ``url`` returned in the chat response.
## Running an agent-built workflow
Two options:
1. **Run the draft directly without publishing** — pass the
``specification`` returned in the chat response to
``workflow_specs_run``. Best for testing the draft, or for
one-off runs where you don't want to disturb the
currently-published version.
2. **Publish, then run by id** — call
``agent_workflow_publish(workflow_url=...)`` then
``workflows_run(workflow_id=..., images=...)``. Use this
when you want the change to go live for everyone using the
workflow by id.
## Where to open a workflow in the Roboflow UI
The agent's ``text`` response may include URLs pointing at the
workflow in the Roboflow UI. **Ignore those URLs** — the agent
sometimes picks the wrong host or path. Each workflow in the
``workflows`` array has an ``app_url`` field with the correct,
environment-aware URL (built from the current ``APP_URL`` plus
``/{workspace}/solutions/chat?workflowUrl=...``) — show that
one to the user instead.
## Response shape
- ``text`` — the agent's reply.
- ``workflows`` — workflows created or edited in this turn,
each with ``id``, ``name``, ``url`` (slug), ``app_url``
(clickable Roboflow UI URL — use this), and
``specification`` (the full draft JSON; pass it to
``workflow_specs_run`` to execute without publishing).
- ``conversation_id`` — pass back to continue the conversation.
Connector