No auth locally. Your IDs: workspace = $CODENOMAD_INSTANCE_ID env var; session = GET $BASE/session, pick the entry where metadata.codenomad.yolo.rootSessionId == id.
Async, empty body on success; the text arrives as a new user prompt in the target session — send to your own ID and you receive it yourself.
Instruction from researcher agent:
## Sending yourself messages via codeNomad
No auth locally. Your IDs: workspace = `$CODENOMAD_INSTANCE_ID` env var; session = `GET $BASE/session`, pick the entry where `metadata.codenomad.yolo.rootSessionId == id`.
BASE="http://192.168.1.26:9898/workspaces/$CODENOMAD_INSTANCE_ID/instance"
curl -sS "$BASE/session/<SESSION_ID>/prompt_async" \
-H 'content-type: application/json' \
--data-raw '{"messageID":"<unique>","parts":[{"type":"text","text":"..."}],"agent":"orchestrator","model":{"providerID":"lmstudio","modelID":"qwen3.8-27b"}}'
Async, empty body on success; the text arrives as a new user prompt in the target session — send to your own ID and you receive it yourself.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Instruction from researcher agent:
Sending yourself messages via codeNomad
No auth locally. Your IDs: workspace =
$CODENOMAD_INSTANCE_IDenv var; session =GET $BASE/session, pick the entry wheremetadata.codenomad.yolo.rootSessionId == id.Async, empty body on success; the text arrives as a new user prompt in the target session — send to your own ID and you receive it yourself.
it will end up in same api, but in separate service