Interfaces
The surface people use. Declare a portal over your deployment and Swirls hosts a workspace built from the rooms, reports, and requests you reference.
What it is. The primitives that put a face on your system. Every other category declares what the system is; interfaces declare who it is for.
Use it when the people who need your system are not the people who wrote it. A support team needs the triage agent and the ticket report, not the dashboard that operates them.
- Portal: a fixed, hosted workspace over your deployment. Declare sections that reference the channels, views, and workflows your team can reach. Swirls hosts the shell and renders it with live data.
A deployment already describes a complete system: agents that reason, workflows that run, views over the data they produce. A portal block turns that description into a place people actually work: rooms to talk to your agents, reports over your views, and requests that launch your workflows. Add a view block to your files, reference it from a section, and the portal grows a report. The workspace stays in sync with the system because it reads straight from what you deployed.
Audit log
The append-only record of who did what across your organization. Read it on the Audit page in the dashboard or query it with the SDK using cursor pagination.
Portal
A workspace where your team, or your client's team, talks to the agents you built. Declare the sections, channels, views, and workflows it holds; Swirls hosts the shell.