Pulse Agent
Chat with Pulse Agent in the app, manage sessions, and configure workspace agent settings.
Pulse Agent
Pulse Agent is Pulse's in-app AI assistant — multi-turn chat that can read workspace context, use approved tools, and help with planning and execution when enabled for your workspace.
Pulse Agent requires the workspace ai_workflows capability and the pulse_agent feature flag. MCP client setup is documented separately under Integrations.
Open the agent
- Sidebar quick action Agent →
/agentfor a new chat /agent/{sessionId}resumes an existing session- Agent panel may dock on entity pages where the product embeds it
Sessions persist until you delete them or workspace retention policy removes them.
What the agent can do
Capabilities depend on workspace configuration:
- Answer questions about issues, projects, and goals you can already access
- Use connectors and loopback tools the admin approved
- Read knowledge sources indexed for the workspace or team
- Propose actions that respect your permissions (the agent cannot bypass ACL)
The agent runs on models and endpoints configured by admins — not on a fixed public model.
Settings overview
| Audience | Path | Purpose |
|---|---|---|
| You | Settings → Agent personalization | Personal defaults, knowledge, skills |
| Members | Settings → Pulse Agent | Workspace agent hub |
| Workspace managers | Settings → Pulse Agent → Workspace | Workspace-scoped routing, knowledge, repos |
| Platform admins | Settings → Pulse Agent → Admin | Providers, model bindings, infrastructure |
| Team managers | Settings → Your teams → <team> → Agent | Team-scoped agent config |
Sections include General, Models, Knowledge, Repositories, Connectors, Routing, Secrets, and Effective (resolved config preview).
Knowledge and code intelligence
- Knowledge — documents and sources the agent may retrieve (RAG)
- Code intelligence — indexed repositories for code-aware answers (workspace manager setting; separate kill switch in deployment)
These are distinct from Documents you edit manually — knowledge settings define what the agent may index.
MCP vs in-app agent
| In-app Agent | MCP server | |
|---|---|---|
| Where | /agent in Pulse | Claude Code, Cursor, Codex, … |
| Auth | Your Pulse session | OAuth / tokens per client guide |
| Setup doc | This page | MCP server |
Use both when your organization allows — they share workspace policy but different clients.
Next
- Integrations → MCP server — external AI clients
- Administration — enable capabilities
- Documents — content the agent may reference
Last updated on