Agent Studio Overview
Agent Studio is the visual and operational interface for Smartunit agents. It turns deployed Node-RED agent configuration and runtime data into graphs, dashboards, session traces, memory records, and alerts.
Early-stage notice: Agent Studio is in active development. Visual editing is currently limited, and labels or workflows may change. Use the full Node-RED flow editor as the source of truth for agent configuration.
| Route | View | Purpose |
|---|---|---|
/ | Dashboard | Sessions, events, cost, tokens, and activity. |
/agents | Agents | Agent graph and selected configuration details. |
/events | Events | Session list and event chain. |
/memory | Memory | Session facts and memory records. |
/alerts | Alerts | Agent alerts by severity and source. |
What Studio Is For
Section titled “What Studio Is For”Use Agent Studio to:
- See which configuration, skills, and sub-agents belong to an agent.
- Compare session, event, token, and provider-reported cost activity.
- Follow the event chain for one session.
- Inspect memory facts and rolling summaries.
- Review alerts by agent, severity, and source.
Studio does not replace Node-RED flow wiring. The Edit action in the Agent Graph opens the full Node-RED flow editor when you need to change fields or wire tool flows that are not available in Studio’s limited editor.
How The Agent Graph Maps To Node-RED
Section titled “How The Agent Graph Maps To Node-RED”| Studio card | Node-RED source |
|---|---|
| Agent | agent |
| Behaviour | agent-behaviour |
| Model | agent-model |
| Connection | agent-connection |
| Memory | agent-memory |
| Budget | agent-budget |
| Skills group | Visual grouping created by Studio |
| Skill | agent-skill |
The Skills group is a Studio visualization, not a deployable Node-RED node.
agent-in and the flow logic behind a skill are also not shown in the agent
configuration graph.
Data Shown In Studio
Section titled “Data Shown In Studio”Studio can show user messages, model responses, tool results, memory records, usage totals, warnings, errors, and alerts. Treat screenshots and exports as sensitive unless they have been reviewed.
Safe Use
Section titled “Safe Use”- Do not share screenshots that include real user messages, private memory records, API keys, internal URLs, or customer data.
- Use test sessions when creating examples for docs or support.
- Enable debug mode only when a trusted operator needs deeper troubleshooting detail.