Launch

How Burp starts Cursor Agent (agent acp) and where the Agent’s working directory points.

Configure under Cursor Agent → Settings → General.

Launch profiles

Profile	When to use
Native (label may say Native (recommended) or Native (Windows))	Burp and agent on the same OS
WSL / WSL (recommended)	Windows Burp with agent installed inside WSL (Windows Burp only)
Custom override	You supply the full command

Defaults: Windows Burp → WSL; otherwise Native.

If Burp itself runs inside WSL, use Native (Linux). Do not pick the WSL profile to nest another wsl.exe hop.

Typical resolved commands:

• Native: agent acp
• WSL: wsl.exe -e agent acp (bare agent may be rewritten to an absolute Linux path)

SHELL: the extension sets SHELL=/bin/bash for the Agent process (Native env, or env SHELL=/bin/bash on the WSL bridge) so tool shells behave predictably.

Session cwd vs process cwd

Two different directories:

Directory	Meaning
Session cwd	Where Cursor Agent treats as its workspace for tools/shells (inside WSL when bridged)
Process cwd	Working directory of the OS process that launches agent / wsl.exe

Session cwd resolution:

1. Your Session cwd override in Settings, if set
2. Else $HOME/BurpSuite if that folder exists
3. Else $HOME

(For WSL, home / BurpSuite existence is probed inside the Linux environment.)

Process cwd for WSL bridges must be a Windows path or the platform default — never a Linux path like /home/.... That mismatch causes CreateProcess error 267. Session cwd can still be /home/... inside WSL; that is separate.

Launch preview

Settings shows Launch preview with the resolved argv, processCwd, and sessionCwd. Use it after changing profile, override, or cwd.

There is no separate “diagnostics panel”; process logs go to Burp’s extension output / Event log.

Agent discovery (WSL)

With the WSL profile, a bare agent token is often missing from non-login PATH. The extension probes with a login-style command -v agent and rewrites to an absolute Linux path when possible. Prefer installing/logging in so that probe succeeds.

GUI Burp on Linux/macOS can also miss login-shell PATH — use an absolute path or Custom override if Native fails.

Resume after ACP load miss

Burp keeps the visible transcript in project prefs. Cursor Agent’s native session memory is separate.

After extension unload, process death, or a failed session/load:

1. The next send may create a new ACP session.
2. A system notice appears in the chat.
3. The extension can prepend a briefing from the Burp transcript so the Agent isn’t starting blank.

Settings → Resume briefing:

Mode	Behavior
Compact briefing	Recent turns + tool names (default lean handoff)
Full transcript	Larger transcript excerpt (still capped; not an infinite dump)

Resume on the notice/error strip re-briefs without waiting for another failure. Prefer Resume over pasting the whole chat by hand.

Clearing a chat drops the stored ACP id (next send = brand-new Agent session). See sessions.md.

What Burp keeps vs what Agent may lose

Kept in Burp (project)	May reset when ACP can’t load
Messages, title, pin, draft, unread	Agent-native tool/context memory for that ACP id
Exported session JSON (without live process state)	Same — import clears ACP id

First checks

1. agent login (or your org auth) in the same environment Burp will use.
2. Pick the right launch profile; confirm Launch preview.
3. Set session cwd to your hunt folder when you want shells/file tools to start there.
4. Send a one-line probe in a new chat.

Failures: troubleshooting.md.

Related

• Install · Sessions · MCP · Troubleshooting