Coding sessions

Overview

Coding sessions are the workspace settings for hosted code changes. Workspace admins pick the agent and model, attach one reusable environment per repository, enroll runtimes, and store secrets the session can read.

Pulse Agent can start a runner from chat. Open that session at /runner-sessions/{id}. Opening an issue in an editor is a different job — Work on issue (W then O) on Assign and delegate issues, configured under Code & reviews.

Setup

Open Settings → AI & Agents → Coding sessions (/settings/pulse-agent/coding-sessions).

The page groups:

• Agent and model defaults
• Environments
• Runtimes
• Secrets

Manage credits opens Settings → Usage & limits (/settings/plan/usage). Members can read environments; only workspace managers and platform admins can change them.

Choose a model

The Agent row is the CLI Pulse uses for hosted sessions. The catalog comes from the server — commonly Claude Code and Codex, with unavailable rows marked.

Model may affect quality and cost. Auto lets the agent CLI pick. Changing the agent resets the model to Auto.

Environment rows can inherit the workspace agent and model, or pin their own.

Configure coding environments

An environment tells every coding session on one repository what to install, which tools to pin, and which variables to set. It applies on top of the repository's own .pulse/sandbox.json.

Each repository can have one active environment. New environment creates one. Archive stops it applying to new sessions and frees the repository so you can create another.

If no environment exists, sessions use the repository's own .pulse/sandbox.json.

Configure an environment

On New environment or an existing row:

1. Choose the Repository (frozen after create — archive and start over to switch)
2. Optionally pin Agent and Model, or leave Inherit
3. Add a Prepare script, Tool versions, files, and variables under Setup
4. Add Custom guidance if the session needs repository-specific instructions
5. Create environment or Save changes

Archived environments stay listed for sessions that already ran under them. They cannot be edited.

Limitations

• One active environment per repository
• Coding sessions clone from a cloud runtime — a GitLab repo reachable only through Pulse Bridge cannot be used until it is connected directly
• Loops cannot run a Coding session or Repository knowledge capability in the current release

Guidance and skills

Workspace, team, and personal Pulse Agent skills and guidance still apply. Environment Custom guidance is extra instruction for sessions on that repository.

AI credits

Hosted sessions draw from the workspace AI allowance. Open Manage credits on the coding sessions page, or go to Settings → Usage & limits.

FAQ