Repository-aware coding

Pulsar Code

A natural-language coding workflow with repository evidence, isolated execution, reviewable changes, checks, and explicit approval gates.

Key considerations

Explain first

Ask about files, architecture, failures, or behavior with repository context.

Prepare evidence

Review files read, artifacts, changes, and checks before approving a write.

Gate risk

Package, network, pull-request, and write-capable workflows remain explicit.

Pulsar Code showing a secret-scanned repository diff and explicit approval gate.
Pulsar Code keeps repository evidence, proposed changes, branch state, and approvals in one reviewable task.

Architecture at a glance

Repository and editor context
Policy-owned task plan
Isolated runner and evidence
Human review and approval

A simple task surface over a controlled workflow

The product interface presents this workflow as Pulsar Code. Users describe a repository goal in plain language while the agent gathers approved context, plans the task, records evidence, and presents results without requiring the user to manage the underlying runner or policy machinery.

Read-only work stays efficient

Repository explanations, file inspection, tree navigation, and workspace-safe context can run without turning every question into a write workflow. Generated, oversized, unsupported, and secret-like files are filtered from indexing.

Changes remain reviewable

When a task proposes a patch, Pulsar Code preserves file evidence, diff context, checks, artifacts, and task history. The user can inspect the result before any pull request or other write-capable action is approved.

Local and remote boundaries remain visible

The VS Code bridge can supply editor context and diagnostics while storing its API key in VS Code Secret Storage. Local file changes or commands require permission, and backend execution remains behind repository policy and the approved runner.

Not arbitrary model-driven execution

Model output does not bypass policy. Unsafe patches, package work, network access, pull requests, plugin execution, and secrets remain controlled by backend validation, task state, redaction, and approvals.

Private deployment consultation

Review Pulsar against your environment.

Bring the infrastructure, security boundaries, model runners, and use cases. The Pulsar team will map the appropriate deployment path.

Request a deployment review

Product screenshot

Open full resolution