Guide / Check your work
AI agents of Camunda 8
Every AI agent task and agent sub-process of a Camunda 8 project, read in one place: its model, limits, memory, tools and MCP clients, with checks for what is wrong.
Not the same as the agents of the AI chat
This page is about the AI agents you draw in a Camunda 8 process, the AI agent task and the AI agent sub-process. They run in the engine. The page AI agents is about the programs that answer the AI chat in the editor. The two are unrelated.
See the agents of a project
Free, with no time limit.
penstock agents [folder] [--format text|json]
It lists every AI agent task and agent sub-process with:
- the model and the provider, the limits and the memory;
- the tools, with the
fromAi()parameters the model fills in; - the MCP clients the agent uses, and whether their configuration is found;
- the tool filters.
It prints only names, never values. It exits 0 when no agent has an error, and 1 when an agent has an error or the folder does not exist. The agents MCP tool does the same for an AI assistant.
The Agents tab and screen
The sidebar of the BPMN editor has an Agents tab. An Agents screen shows the whole project. Each agent has its model, prompts (FEEL highlighted), tools with their fromAi() parameters, MCP clients with the status the connections map gives, memory, response format and human approval. The Problems tab shows the agent findings too. Penstock Web has a sidebar entry. This is free, with no time limit.
Where the Agents screen is, by tool
JetBrains
An action under Tools opens the Agents screen of the project. The Agents tab is in the sidebar of the BPMN editor.
VS Code
A command opens the Agents screen of the project. The Agents tab is in the sidebar of the BPMN editor.
Command line
penstock agents lists the agents. See agents.
The checks
Nine rules in the family agents, each with a page. They also run in penstock check.
| Rule | What | Level |
|---|---|---|
agents/no-model-call-limit | No limit on model calls. | Advice |
agents/tool-without-description | A tool without a description. | Advice |
agents/fromai-incomplete | A fromAi parameter without a type or description. | Advice |
agents/tool-filter-matches-nothing | A tool filter that matches nothing. | Advice |
agents/duplicate-tool-names | Two tools or clients with the same name. | Advice |
agents/adhoc-without-agent | A tool container no agent uses. | Advice |
agents/mcp-client-no-config | An MCP client nobody configured. | Error |
agents/plain-text-secret | An API key typed into the diagram. | Error |
agents/deprecated-template | A deprecated template version. | Advice |
Move agents to the 8.10 templates
Pro to write
penstock migrate agents [paths] [--write] [--format text|json]
It moves agent elements from the 8.9 and older template versions to the 8.10 agent task and agent sub-process templates, by the migration rules the new templates declare. It is a dry run by default. An element whose mapping cannot be proven is left untouched and listed with the reason. The first 3 elements of the preview are free. --write replaces the files atomically and is part of Pro. The migrate_agents MCP tool does the same for an agent.
On an agent card, Migrate to the 8.10 template rewrites that agent in the open diagram after a confirmation. Save the diagram to keep it. Make scenario next to it adds the scenario with a stubbed model. Both are Pro, and what cannot be proven is left untouched and said so.
A scenario with the model stubbed
penstock agents scenario processes/support.bpmn --write
For an AI agent process it makes a scenario in which the agent job is completed with a canned answer, and it asserts that the agent completes and that no tool runs. For an agent sub-process it writes the COMPLETE_JOB_AD_HOC_SUB_PROCESS step that Camunda Process Test runs. Previewing is free. --write adds the scenario to the diagram's scenarios and is part of Pro, and Team in a pipeline. --agent <id> limits it to one agent. See Scenarios.
Common problems
- The command lists no agent.
- It reads Camunda 8 files with AI agent task or agent sub-process elements. Check the folder and the engine of the project.