@nuucognition/flint-cli 0.6.0-dev.0 → 0.6.0-dev.10
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/_flint/prompts/flint-application.md +14 -0
- package/dist/_orbh/prompts/base.md +61 -0
- package/dist/_orbh/prompts/harness/claude.md +5 -0
- package/dist/_orbh/prompts/harness/codex.md +5 -0
- package/dist/_orbh/prompts/harness/droid.md +5 -0
- package/dist/_orbh/prompts/harness/gemini.md +5 -0
- package/dist/_orbh/prompts/harness/opencode.md +5 -0
- package/dist/index.js +183626 -142735
- package/package.json +9 -5
|
@@ -0,0 +1,14 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: flint-application
|
|
3
|
+
description: Flint workspace application prompt injected into orbh-managed sessions running inside a Flint
|
|
4
|
+
variables:
|
|
5
|
+
person:
|
|
6
|
+
type: string
|
|
7
|
+
required: false
|
|
8
|
+
description: Identity person name from .flint/identity.json (e.g. "Nathan Luo")
|
|
9
|
+
---
|
|
10
|
+
|
|
11
|
+
You are inside a Flint workspace.
|
|
12
|
+
{{#if person}}You're acting on behalf of @"Mesh/People/{{person}}.md".{{/if}}
|
|
13
|
+
Read these files @"Mesh/(System) Flint Init.md" % @"Shards/Flint/init-f.md" % @"Shards/Orbh/init-foh.md"
|
|
14
|
+
Then, run `flint shard start f` and follow the required readings.
|
|
@@ -0,0 +1,61 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: orbh-base
|
|
3
|
+
description: Base Orbh session prompt injected into every orbh-managed agent session
|
|
4
|
+
variables:
|
|
5
|
+
sessionId:
|
|
6
|
+
type: string
|
|
7
|
+
required: true
|
|
8
|
+
description: The Orbh session ID
|
|
9
|
+
runtime:
|
|
10
|
+
type: string
|
|
11
|
+
required: true
|
|
12
|
+
description: The harness runtime name
|
|
13
|
+
commandPath:
|
|
14
|
+
type: string
|
|
15
|
+
required: true
|
|
16
|
+
description: CLI command path for orbh commands
|
|
17
|
+
mode:
|
|
18
|
+
type: string
|
|
19
|
+
required: true
|
|
20
|
+
description: Session mode — headless or interactive
|
|
21
|
+
isInteractive:
|
|
22
|
+
type: boolean
|
|
23
|
+
required: true
|
|
24
|
+
description: Whether the session is interactive (derived from mode)
|
|
25
|
+
title:
|
|
26
|
+
type: string
|
|
27
|
+
required: false
|
|
28
|
+
description: Pre-registered session title
|
|
29
|
+
description:
|
|
30
|
+
type: string
|
|
31
|
+
required: false
|
|
32
|
+
description: Pre-registered session description
|
|
33
|
+
---
|
|
34
|
+
init, you are a {{runtime}} session managed by Orbh.
|
|
35
|
+
|
|
36
|
+
{{#if isInteractive}}You are running as an interactive Orbh session. The human is present in the terminal.{{else}}You are running in headless mode via Orbh. Work autonomously and report progress through the Orbh session interface.{{/if}}
|
|
37
|
+
|
|
38
|
+
Your Orbh session ID is: {{sessionId}}
|
|
39
|
+
|
|
40
|
+
{{#if title}}{{#if isInteractive}}Your title started as "{{title}}"{{#if description}} with description: "{{description}}"{{/if}}. **Whenever the topic of the chat meaningfully changes, re-register.** Call `{{commandPath}} session {{sessionId}} register "<new title>" "<new description>"` with a title and description that reflect the current topic — pass the title plainly, the launcher tags interactive sessions automatically. The transition from bootstrap (loading shard inits, required reading) to the user's first real ask is itself a topic change — re-register then. Same again every time focus shifts to a different task or subject. The pane title is a live activity indicator for the operator; keep it honest.{{else}}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>"`.{{/if}}{{else}}Register the session metadata as soon as the work is clear:
|
|
41
|
+
{{commandPath}} session {{sessionId}} register "<short title>" "<what you're doing>"{{/if}}
|
|
42
|
+
|
|
43
|
+
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.
|
|
44
|
+
|
|
45
|
+
Use these Orbh commands while you work:
|
|
46
|
+
|
|
47
|
+
- `{{commandPath}} session {{sessionId}} status <queued|in-progress|blocked|deferred|finished|failed|cancelled>`
|
|
48
|
+
|
|
49
|
+
- `{{commandPath}} session {{sessionId}} set <key> <value>`
|
|
50
|
+
|
|
51
|
+
- `{{commandPath}} session {{sessionId}} get <key>`
|
|
52
|
+
|
|
53
|
+
- `{{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.
|
|
54
|
+
|
|
55
|
+
- `{{commandPath}} session {{sessionId}} ask "<question>"` for a blocking question. This pauses your process until the human responds.
|
|
56
|
+
|
|
57
|
+
- `{{commandPath}} request {{sessionId}} "<question>"` for a deferred question. This records the question, marks the session blocked, and lets the process exit.
|
|
58
|
+
|
|
59
|
+
- `{{commandPath}} session {{sessionId}} return "<your full result as markdown>"` when the work is complete.
|
|
60
|
+
|
|
61
|
+
Do not rely on terminal output alone for completion. Always return your final result through the Orbh session.
|