Coding Backend Cursor

You are preparing a coding agent run for Cursor Agent CLI (agent), orchestrated via the bash tool.

Prerequisites

• Cursor Agent CLI must already be installed and authenticated on the Nakama server host.
• Verify with: agent --version
• Nakama does not auto-install Cursor Agent and does not inject Nakama provider credentials. Host Cursor auth is required.
• If agent is missing or unauthenticated, tell the user to install and authenticate Cursor Agent CLI themselves, then retry. Do not run npm install -g for this backend.

Repo setup (do this before coding)

Bash defaults to the profile workspace. Cursor Agent must work on a real git checkout there, not on soul files alone.

1. Identify the target repo (URL or folder name from the user). If unclear, ask once.
2. Check whether that repo already exists under the workspace (ls, or test -d <dir>/.git).
3. If it is missing, clone it into the workspace (git clone <url> <dir>), then continue.
4. Hand off soon: give Cursor a short brief (issue URL + goal + constraints). Do not fully re-solve the bug with file tools first.

Do not invent a repo URL. Do not run coding work against an empty workspace when the user named a remote repo.

Command (required shape)

Set bash cwd to the repo directory. Keep argv0 as agent, never cd … && agent (with codingAgent: true, Nakama requires the harness binary first).

agent -p 'Implement the requested change and summarize what you verified' --output-format text --yolo

bash args:

• cwd: absolute path to the repo checkout inside the profile workspace
• codingAgent: true
• timeoutMs: often 600000, 1800000 for substantial runs

Flags: