feat(dkai-agent): add slashbay-pull helper

[surrealwolf]

Summary

• Workspace parameters slashbay_url and slashbay_worker_token inject SLASHBAY_URL / SLASHBAY_WORKER_TOKEN via coder_env (same pattern as cursor_api_key).
• Startup writes /home/coder/bin/slashbay-pull and nohups it when both are set. Logs /tmp/slashbay-pull.log, pid /tmp/slashbay-pull.pid.
• Loop: claim → progress cloning → clone git_url into /home/coder/agent-workspace/git/<repo>/ → progress agent_running → agent -p → complete/failed.
• Leaves start-cursor-worker in place. Does not put CODER_TOKEN in the workspace.

Pairs with DataKnifeAI/slashbay pull-jobs API.

Test plan

• make test / scripts/check-dkai-startup-shell.sh (startup_script bash -n)
• Push template, create a workspace with both Slashbay params + cursor_api_key
• Confirm /tmp/slashbay-pull.log shows claims against Slashbay
• Confirm start-cursor-worker still autostarts when cursor_api_key is set

Made with Cursor

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 3 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 1b5dd70. Configure here.}

[cursor]

Agent cannot apply code changes

High Severity

slashbay-pull invokes agent -p without --force (and without --trust). In Cursor headless/print mode, writes and other tools are denied unless forced, so issue jobs can exit 0, get marked complete, and leave the repo unchanged.

 

^{Reviewed by Cursor Bugbot for commit 1b5dd70. Configure here.}

[cursor]

Restart orphans agent processes

High Severity

Startup only kills the slashbay-pull bash PID from the pidfile, with no process-group cleanup, no wait, and no sleep before relaunch. Mid-job agent -p and the heartbeat subshell keep running, so restarts leave orphans and can double-claim work.

Additional Locations (1)

• templates/dkai-agent/main.tf#L623-L632

 

^{Reviewed by Cursor Bugbot for commit 1b5dd70. Configure here.}

[cursor]

Bad claim JSON kills puller

Medium Severity

After a HTTP 200 claim, set -e is re-enabled and job_field parses /tmp/slashbay-claim.json with no error guard. Invalid JSON or a non-object body makes Python fail and exits the whole while true daemon until the workspace is restarted.

Additional Locations (2)

• templates/dkai-agent/main.tf#L527-L536
• templates/dkai-agent/main.tf#L580-L581

 

^{Reviewed by Cursor Bugbot for commit 1b5dd70. Configure here.}

[cursor]

Left a non-blocking comment; not approved. Cursor Bugbot finished skipped and reported 3 unresolved findings that need human review. No additional reviewers were assigned.

  

_{Sent by Cursor Approval Agent: Pull Request Router and Approver}