The agent builder is the workspace for creating agent workflows. Use it when you need to define how an agent behaves, what tools it can use, and how it connects to other agents.

Main tasks

  • Create an agent workflow.
  • Edit agent configuration.
  • Connect nodes on the canvas.
  • Review workflow history.
  • Save changes before running the agent.

Workflow types

Pinter supports several workflow shapes: The builder canvas exposes the sequential, parallel, and loop shapes. The backend also supports two additional orchestration types configured through the agent API: conditional (routes between branches based on a condition) and human-in-the-loop (pauses for human confirmation). See Backend and ADK architecture for the full agent type table.

Generate instructions with AI

The instruction fields appear as expandable sections for identity, mission, methodology, boundaries, and examples. Open a section to edit it, or use Generate with AI to fill all five fields from a short brief.
1

Open the generator

Select Generate with AI next to the instruction fields. The Generate Instruction dialog opens.
2

Describe the agent

Write a short brief of what the agent should do.
3

Review the generated fields

Pinter fills all five instruction fields: identity, mission, methodology, boundaries, and examples. Expand each section to review and edit the result before saving.
Backend endpoint:

Version history

The history panel shows Published Versions alongside the Active Canvas Copy (Draft). Use it to:
  • Compare instruction changes between versions with the field-level diff view.
  • Restore an earlier version when a change regresses agent behavior.
Publish a version when the agent is ready for users; keep iterating on the draft without affecting the published version.

Share an agent

Use Share Agent in the canvas header to give other users access directly or through claim codes. See Sharing agents.

Builder route

Open the builder from the application navigation or go to:
Specific agents open under:

Good builder practice

Start with one agent and one tool. Add workflow structure only when the task needs it.
Keep each agent focused on one responsibility. Smaller agents are easier to test and reuse.