feat(coding-agent): add public agent creation command - #1991
Conversation
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 63f4875. Configure here.
| ) { | ||
| return fail(`Usage: ${APP_NAME} ${getCommandSpec(["create"])!.usage}`); | ||
| } | ||
| return runInternalAgentCommand("create", args.slice(1)); |
There was a problem hiding this comment.
Cold create can fail to connect
High Severity
Public create only kicks off a fire-and-forget early daemon launch, then DaemonClient.connect runs immediately. That connect fails as soon as the socket is missing, so a cold prime-agent create can error while the background service is still starting. Interactive startup awaits ensureInteractiveDaemonRunning, and runOpen starts the daemon if needed; this path does neither.
Additional Locations (2)
Reviewed by Cursor Bugbot for commit 63f4875. Configure here.
1 participant
Summary
prime-agent create [options] [name] -- <message>commandContext
PR #423 intentionally removed the public
prime-agent daemon ...hierarchy in favor of task-oriented commands. Automation that created top-level sessions withdaemon createanddaemon promptthen had no supported replacement, whilelist,send,attach, and other agent operations did.This adds the missing task-oriented operation without restoring the old daemon command group. It is a backward-compatible CLI addition and does not change the daemon protocol or response schema.
Linear: RES-1256
Related: #423
Validation
cd packages/coding-agent && npx tsx ../../node_modules/vitest/dist/cli.js --run test/daemon-command.test.ts test/daemon-launch.test.ts test/public-command.test.ts(85 passed)npm run check