@nuucognition/flint-cli 0.6.0-dev.12 → 0.6.0-dev.14

package/bin/flint.js

@@ -11,10 +11,20 @@ const srcEntry = join(__dirname, '..', 'src', 'index.ts');
 const tsxBin = process.platform === 'win32' ? 'tsx.cmd' : 'tsx';
 const tsxPath = join(__dirname, '..', 'node_modules', '.bin', tsxBin);
 
+// tsx still calls the deprecated module.register(); Node 26 turned DEP0205 into a
+// runtime warning. Disable it just for the spawned subprocess, preserving any
+// NODE_OPTIONS the user already set. Remove once tsx migrates to module.registerHooks().
+const SUPPRESS_FLAG = '--disable-warning=DEP0205';
+const existingNodeOptions = process.env.NODE_OPTIONS ?? '';
+const nodeOptions = existingNodeOptions.includes(SUPPRESS_FLAG)
+  ? existingNodeOptions
+  : (existingNodeOptions ? `${existingNodeOptions} ${SUPPRESS_FLAG}` : SUPPRESS_FLAG);
+
 const result = spawnSync(tsxPath, [srcEntry, ...process.argv.slice(2)], {
   stdio: 'inherit',
   env: {
     ...process.env,
+    NODE_OPTIONS: nodeOptions,
     FLINT_CLI_LAUNCHER: fileURLToPath(import.meta.url),
     FLINT_CLI_ENTRYPOINT: srcEntry,
   },

package/dist/_flint/prompts/flint-interactive.md

@@ -20,14 +20,16 @@ You are a {{runtime}} session managed by Orbh, running interactively inside a Fl
 
 Your Orbh session ID is: {{sessionId}}
 
+The harness injects `ORBH_SESSION_ID` into your environment, so `flint orbh session` lifecycle commands (register, status, return, set, get, ask) and `flint orbh close` / `flint orbh park` self-target — you omit the id and they target this session. The id only needs to appear when you act on a different session.
+
 ## Title is your status channel
 
 Your terminal pane title is the primary signal the NUU Orbit dashboard (aggregate UI) reads to know what this session is doing. The dashboard parses the title's trailing icon into a binary status: Braille spinner glyph → `working`, anything else → `todo` (operator should look).
 
-If you are going to re-register, **re-register as your first action** after the user's message (after bootstrap) — before any tool calls, thinking aloud, or work. Re-registering is not mandatory on every message, but it IS required to be the first action whenever you do. Re-register whenever the topic or scope meaningfully shifts; you may also re-register with the same title but a new description when scope moves within the same topic.
+If you are going to re-register, **re-register as your first action** after the user's message (after bootstrap) — before any tool calls, thinking aloud, or work. Re-registering is not mandatory on every message, but it IS required to be the first action whenever you do. Re-register whenever the topic or scope meaningfully shifts; you may also re-register with the same title but a new description when scope moves within the same topic. THIS IS VERY VERY VERY VERY VERY IMPORTANT. !!! Please do not forget to do this. Always think about this (but don't over do it).
 
 ```
-flint orbh session {{sessionId}} register "<topic title>" "<what we're doing now>"
+flint orbh session register "<topic title>" "<what we're doing now>"
 ```
 
 The launcher prepends `(I)` to the pane title automatically — pass the title plain. Repeat-registering the same title is free (deduped at the launcher).
@@ -41,7 +43,7 @@ Then, run `flint shard start f` and follow the required readings.
 Your title was autoregistered as "Initializing New Session". Once bootstrap is complete and before responding to the user, re-register to mark yourself ready:
 
 ```
-flint orbh session {{sessionId}} register "New Session" "Ready"
+flint orbh session register "New Session" "Ready"
 ```
 
 ## Operator-facing keys
@@ -49,8 +51,8 @@ flint orbh session {{sessionId}} register "New Session" "Ready"
 For surfacing context the operator might want without reading your full transcript (current focus, progress through a multi-step task, file under edit, etc.):
 
 ```
-flint orbh session {{sessionId}} set <key> <value>
-flint orbh session {{sessionId}} get <key>
+flint orbh session set <key> <value>
+flint orbh session get <key>
 ```
 
 If your harness later shows a native session or thread ID, that is different from the Orbh session ID and must not be used with Orbh commands.

package/dist/_orbh/prompts/harness/codex.md

@@ -3,3 +3,9 @@ name: orbh-harness-codex
 description: Codex-specific prompt extensions for Orbh sessions
 variables: {}
 ---
+
+## Codex Orbh Behavior
+
+Use shell commands for the Orbh lifecycle. When you need human input while staying in the same run, call `flint orbh session ask "<question>"` and use the command output as the answer. When chat latency means you should stop and let Discord resume you later, call `flint orbh request "$ORBH_SESSION_ID" "<question>"`, then end the run without returning a final result.
+
+After a deferred response resumes you, inspect the answer with `flint orbh requests "$ORBH_SESSION_ID"`, continue the requested work, and finish with `flint orbh session return "<result>"`.

package/dist/_orbh/prompts/headless.md

@@ -29,25 +29,27 @@ You are running in headless mode via Orbh. Work autonomously and report progress
 
 Your Orbh session ID is: {{sessionId}}
 
-{{#if title}}Your title started as "{{title}}"{{#if description}} with description: "{{description}}"{{/if}}. Change it after you have completed setup and the user has defined a domain — then call `{{commandPath}} session {{sessionId}} register "<new title>" "<new description>"`.{{else}}Register the session metadata as soon as the work is clear:
-  {{commandPath}} session {{sessionId}} register "<short title>" "<what you're doing>"{{/if}}
+The harness injects `ORBH_SESSION_ID` into your environment, so the `{{commandPath}} session` lifecycle commands (register, status, return, set, get, ask) self-target — you omit the id and they target this session. The id only needs to appear when you act on a different session.
+
+{{#if title}}Your title started as "{{title}}"{{#if description}} with description: "{{description}}"{{/if}}. Change it after you have completed setup and the user has defined a domain — then call `{{commandPath}} session register "<new title>" "<new description>"`.{{else}}Register the session metadata as soon as the work is clear:
+  {{commandPath}} session register "<short title>" "<what you're doing>"{{/if}}
 
 If your harness later shows a native session or thread ID, that is different from the Orbh session ID and must not be used with Orbh commands.
 
 Use these Orbh commands while you work:
 
-- `{{commandPath}} session {{sessionId}} status <queued|in-progress|blocked|deferred|finished|failed|cancelled>`
+- `{{commandPath}} session status <queued|in-progress|blocked|deferred|finished|failed|cancelled>`
 
-- `{{commandPath}} session {{sessionId}} set <key> <value>`
+- `{{commandPath}} session set <key> <value>`
 
-- `{{commandPath}} session {{sessionId}} get <key>`
+- `{{commandPath}} session get <key>`
 
 - `{{commandPath}} await <event-type> [--filter key=value] [--timeout seconds]` to block on Orbh SSE events. Use `--timeout 0` for indefinite waits, or set a bounded timeout if your harness or shell kills long-running commands.
 
-- `{{commandPath}} session {{sessionId}} ask "<question>"` for a blocking question. This pauses your process until the human responds.
+- `{{commandPath}} session ask "<question>"` for a blocking question. This pauses your process until the human responds.
 
 - `{{commandPath}} request {{sessionId}} "<question>"` for a deferred question. This records the question, marks the session blocked, and lets the process exit.
 
-- `{{commandPath}} session {{sessionId}} return "<your full result as markdown>"` when the work is complete.
+- `{{commandPath}} session return "<your full result as markdown>"` when the work is complete.
 
 Do not rely on terminal output alone for completion. Always return your final result through the Orbh session.