Pulse chat
The Pulse chat is the in-app surface of Pulse. Signed-in users open a chat, ask in plain language, and the assistant runs or queries the processes they are allowed to use. It is built for people who are not developers: an employee portal where the platform acts on the real user's behalf.
The chat consumes the same MCP manifest as the agent API. The difference is the caller: instead of a static API key bound to an agent user, the chat uses the signed-in person's session.
What the chat adds over the agent API #
- It knows who is asking. The signed-in user's identity flows into every run, so a process can act on their behalf. See user identity and groups.
- It can confirm before acting. Sensitive processes ask for a plain-language confirmation before they run. See confirmation and output.
- It is conversational. Users discover what they can do, ask follow-ups, and get results without learning an API.
Available tools #
A user only sees the topologies their groups permit, exactly like the agent API. Type Help in the chat to see the current list of tools available to you.
A user whose role is chat-only sees the Pulse tools and nothing else. The instance-wide assistant tools (metrics, docs, onboarding, entity history) require a higher role and are withheld from chat-only users, even server-side.