Repository navigation
Replies: 4 comments 1 reply
|
Update: added opt-in live proof |
|
Thanks, @smota, for the nodecode runner, the honest "not proved" lines, and the live proof, which found and fixed a real bug that only the live path shows. Option 1, yes: we'd like a small curated entry in Option 2, not now: we're not adding a harness registry or a remote-search command at this point. Separately, openrig.dev/rigs lists ready-to-use team bundles; if you publish a real team that uses One question, for the entry's tested versions: the evidence has grown from the 65 tests in your first post to 72 unit checks plus six live steps at The behavioural scenario: the current "Help wanted" list is in |
|
Wrote up the why: https://github.com/smota/openrig-nodecode/blob/main/WHY.md Short version. OpenRig keeps the seat's chair; nodecode keeps the seat's mind.
Next, pure connector work, no core change: I will keep working on it and experimenting on these ideas. |
|
Option 1 PR: #2859. Exact versions behind the live result:
Not reproduced on unpatched upstream; the entry says so. Scenario: understood, issue first, parked for now. |
Uh oh!
There was an error while loading. Please reload this page.
Built community harness for nodecode - self-evolving Common Lisp agent. Runs as OpenRig seat,
runtime: nodecode. Zero core changes. Repo: https://github.com/smota/openrig-nodecode (Apache-2.0). We run it on our rigs now.What it is
Format-1 preset + runner script, same shape as the dsh example runner. Full runner contract:
launch_resultnodecode rpcfirst framesession_stream_resumed->nativeRef= session id, 0600 fileresumenodecode rpc <ref>; probes gateway first, unknown ref ->error: "missing", exit 3 (nodecode would silently create blank session otherwise)first_inputOPENRIG_FIRST_INPUT+--startup-file-> firststart_turnpasses_modelOPENRIG_MODEL[provider/]model[:effort]->start_turn.requestlaunch_wrapperitem_delta-> throttledactive; tool calls ->PreToolUse; turn end ->Stoporganism.questions<->/api/activity/permission-requestslong-poll <->answer_question<ws>/.agents/skills+<home>/cells/linked-skills/openrig-<seat>Shape
Proof
GET /api/community-harnessesusable: trueagy -> nodecodeready;-> bogusrefusedNot proved: tmux-pane delivery under long-lived seat; model output quality (stub proves plumbing).
Ask
How make this known to community? Options we see:
rig harness list --communitystyle registry (new idea, happy to discuss).Which you prefer? Will follow maintainer call. Also open to PR a behavioural stub scenario for the runner contract if useful (ROADMAP help-wanted).
All reactions