RPC

Reading the port from the store's .owner file and doing the WebSocket handshake yourself

The challenge, the operator token, the session and the subscription are what rpc does for you.

Instead: Spawn nodecode rpc and write commands.

nodecode rpc serve

Exit 2: rpc is a command of its own: nodecode [-p NAME] rpc [SESSION-ID [--cursor N]] [--store PATH | --ephemeral]

Instead: Run nodecode serve, or nodecode gateway on, by itself. nodecode rpc attaches to it.

Spawning one nodecode rpc per prompt

With no organism running, each one starts an organism and stops it when its stdin ends. Every start after a stop sends the model a "running again" note: 6 of the 20 model calls in the runs on this page.

Instead: Keep one nodecode rpc open for your program's life, or run nodecode gateway on so each one attaches.

Writing the prompt as text

invalid JSON: malformed JSON at byte 0: #\s begins no value

Instead: {"type":"start_turn","request":{"prompt":"say pong"}}

Putting prompt beside type

request must be an object

Instead: The prompt goes under request.

Leaving out type

type must be a non-empty string

Instead: Every line names its type.

Steering without expected_turn_id

Rejected: session_id, expected_turn_id, and non-empty prompt are required

Instead: Send the turn_id from your start_turn result.

Taking accepted for the answer

turn admitted came at 0.11 s. The answer's first word came at 1.50 s.

Instead: Read on to the turn's own turn.completed.

Keeping item_delta text as the answer

Deltas are not facts. They have no cursor, and a resume does not send them again.

Instead: The answer is in turn.assistant_message_completed.

Reading sequence as a place in the log

sequence counts the frames sent to this client, and it is 0 on the organism's own frames.

Instead: The place in the log is cursor.

Reading exit 0 as "the turn finished"

Exit 0 means stdin ended. It says nothing about any turn.

Instead: The turn's end is a frame: turn.completed, turn.failed or turn.cancelled.

Expecting rpc's exit to stop a nodecode serve it attached to

An organism that was already serving keeps running, and so does its turn.

Instead: Stop it where you started it, or with nodecode gateway off.

Adding every replay to what you hold

With no resumed_after, the replay is whole: --cursor 9999 got all fifteen facts.

Instead: Replace your copy when resumed_after is absent.

nodecode rpc --cursor 5

Exit 2: --cursor resumes a session past a log position: nodecode rpc SESSION-ID --cursor N

Instead: Name the session first.

--cursor five

Exit 2: --cursor takes a log position, not "five"

Instead: A whole number, from a frame's cursor.