Code & reviews

Set personal coding tools and git-branch defaults for issues.

Overview

Open Settings → Code & reviews (/settings/code-and-reviews). Tools enabled here can be used from the issue page Work on issue menu (W then O).

This page does not turn Reviews on. Reviews is a workspace feature: ask an admin to enable it under Settings → Features, and connect repositories under Settings → Integrations. Personal git identity for reviewing as yourself lives under Settings → Connected accounts — see Profile.

External tools

Configure coding tools

Toggle the apps Pulse can open an issue in:

• Claude Code and Codex CLI — open in your terminal. They require the Pulse desktop app.
• Claude Code desktop, Codex desktop, and Cursor — open in those desktop apps.

You can enable a tool on a machine that cannot run it yet; the menu explains itself until you are on one that can.

Prompt template

Prompt template is the text Pulse uses when opening an issue in a coding tool, or when copying the issue as a prompt. Insert {{issue.identifier}}, {{issue.branchName}}, or {{context}}. Without {{context}} the prompt carries no issue — no description, metadata, or links. Reset to default restores the built-in template.

Custom script

Custom script adds a row to Work on issue. It runs a local command from a coding-tools.json file you choose with Choose configuration file…. It opens in your terminal and requires the Pulse desktop app. macOS asks you to approve the exact command before the first run.

Copy starter configuration puts a starter file on the clipboard. Show in Finder reveals the chosen file. Forget drops it.

Custom link

Custom link adds a web (or confirmed application-scheme) destination to Work on issue. Put {{prompt}} where the issue text should go. Confirm the destination before Pulse will send issue documents there.

Terminal

On the Pulse desktop app, Open coding CLIs in chooses System default, Ghostty, Warp, or iTerm for Claude Code CLI and Codex CLI. The row is hidden where a CLI cannot be launched.

Branch naming

Branch format is the shape of git branch names copied from issues. It follows you across workspaces. Presets include username/identifier-title, identifier-title, feature/identifier-title, and shorter variants. The row shows an example for the current preset.

Move issue to In Progress

Pulse can move an issue to In Progress (the first started status) when you begin work on it. There are separate switches for opening the issue in a coding tool and for copying the git branch name.

Issues already in In Progress, QA, Release, or Done are not moved. Hold Option (Alt on Windows) while performing the action to skip the status change once.

Move the issue to In Progress runs when a coding tool accepts the handoff — not when the deep link fails.

Move issue to In Progress on branch copy

Move issue to In Progress on branch copy runs after you copy an issue’s git branch name. It is a separate switch from the handoff toggle, so copying a branch to paste it somewhere else does not have to start the issue.

Personal GitLab, workspaces, and secrets

The same page also holds personal Pulse Agent resources used for coding sessions and Code Intelligence:

• Personal GitLab connections — connect a GitLab instance and grant repositories for analysis. This is not the Reviews identity on Connected accounts.
• Workspaces — bundle up to 8 repos, then attach the set to a session.
• My Secrets — environment variables for Pulse Agent sessions.

When Pulse Agent is enabled, related personal guidance lives under Settings → Agent personalization.