Skip to content

Getting started with Pulse

This guide takes you from an empty workspace to a working assistant that can run a task on your behalf. It should take about five minutes.

If you are new to the platform, it helps to know where Pulse sits: Studio is where teams build agents, and Pulse is the assistant that runs the work through a single persistent timeline.

1. Open your workspace

Sign in and you land directly in your timeline — the one persistent chat that everything in Pulse revolves around. There are no separate threads to manage; new tasks, results, and approval requests all appear here.

The Pulse onboarding screen, introducing the workspace for chat, files, and background execution

Your first message can be anything you would ask a capable teammate. The Main Agent reads your intent, decides what to do, and either answers immediately or starts background work.

One assistant, one thread

Each person gets a single timeline. This is intentional — it keeps history, context, and pending work in one place instead of scattered across sessions.

2. Connect an integration

Most useful work touches a tool you already use. Open Settings → Integrations and connect a provider — for example Slack, GitHub, Notion, Jira, or Google.

Pulse integrations settings showing available providers such as Google, Notion, Trello, GitHub, and Figma

Authorize the provider with OAuth or an API credential. Once connected, the assistant can read from and act on that system through its tools.

3. Delegate your first task

Ask the assistant to do something concrete. For example:

text
Summarize the open issues in our GitHub repo and post the summary to #standup in Slack.

The assistant will plan the steps, then hand long-running parts to a background worker. You can keep chatting while it runs — progress and results stream back into the timeline.

Pulse task panel showing completed worker-agent tasks alongside the active chat timeline

For recurring work, ask for a schedule:

text
Every weekday at 9:00, send me a digest of yesterday's support tickets.

Pulse registers this as a scheduled task and runs it on cron without further prompting.

4. Approve sensitive actions

When a task would do something consequential — sending an external message, changing a record, spending budget — Pulse pauses and asks first. You can approve from the chat, an email deep-link, or the approvals view. Nothing sensitive happens without your sign-off.

Pending approval cards for creating a file, sending an email, and deleting records — each with Approve and Decline controls

5. Keep what matters

As you work, the assistant stores durable facts in memory and can generate files and artifacts — documents, spreadsheets, slides, or diagrams — that sync across your devices and can be shared with your team.

Pulse memory settings showing memory metrics, search, lifecycle tabs, and stored facts

What's next

Studio · Pulse — Cognipeer product documentation