@ours.network/codex 0.18.0-nightly.1 → 0.18.0-nightly.2
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/.codex-plugin/plugin.json +1 -1
- package/package.json +2 -2
- package/skills/ours/SKILL.md +26 -6
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@ours.network/codex",
|
|
3
|
-
"version": "0.18.0-nightly.
|
|
3
|
+
"version": "0.18.0-nightly.2",
|
|
4
4
|
"description": "Native Codex plugin for secure ours.network messaging and explicitly armed, session-scoped live mail wake.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"license": "FSL-1.1-Apache-2.0",
|
|
@@ -46,7 +46,7 @@
|
|
|
46
46
|
},
|
|
47
47
|
"dependencies": {
|
|
48
48
|
"@modelcontextprotocol/sdk": "^1.29.0",
|
|
49
|
-
"@ours.network/mcp": "0.18.0-nightly.
|
|
49
|
+
"@ours.network/mcp": "0.18.0-nightly.2",
|
|
50
50
|
"@ours.network/sdk": "2.0.1",
|
|
51
51
|
"ws": "^8.21.0",
|
|
52
52
|
"zod": "^3.25.76"
|
package/skills/ours/SKILL.md
CHANGED
|
@@ -79,12 +79,19 @@ allows it for legacy reasons; this skill does not.
|
|
|
79
79
|
|
|
80
80
|
Walk the user through these, checking each. Stop and help at the first one that isn't done.
|
|
81
81
|
|
|
82
|
-
|
|
83
|
-
|
|
84
|
-
|
|
85
|
-
|
|
86
|
-
|
|
87
|
-
|
|
82
|
+
For a first-time or complete host setup, prefer `ours-install`. It installs the
|
|
83
|
+
CLI, one shared daemon, MCP, cowork, Telegram, Fleet, the Human identity, and
|
|
84
|
+
every safely detected harness plugin in one progress-driven flow. It starts the
|
|
85
|
+
daemon and cowork, but deliberately leaves Telegram and Fleet stopped. If
|
|
86
|
+
`~/fleet.yaml` does not exist, it writes a conservative stopped starter with a
|
|
87
|
+
`FleetCoordinator`, watchdog, and coordinator health loop; it never overwrites an
|
|
88
|
+
existing file.
|
|
89
|
+
|
|
90
|
+
1. **Daemon running.** Check it with `ours daemon status`. If the stack is
|
|
91
|
+
missing or incomplete, ask the user to run `ours-install`; use the manual CLI
|
|
92
|
+
package/config/start commands only as a troubleshooting fallback. These are
|
|
93
|
+
operator commands; explain the shared blast radius and obtain consent before
|
|
94
|
+
changing configuration or lifecycle.
|
|
88
95
|
2. **Plugin installed.** Install the native plugin from the ours Codex marketplace, or
|
|
89
96
|
install `@ours.network/codex` globally and run `ours-codex-install`. Start a new
|
|
90
97
|
Codex thread after installation. The native package bundles skills, the ours and
|
|
@@ -121,6 +128,19 @@ the version-matched source of truth:
|
|
|
121
128
|
subcommand's `--help`, and recommend upgrading. Do not ask the user to
|
|
122
129
|
explain available flags or rely on a copied fleet workflow from this skill.
|
|
123
130
|
|
|
131
|
+
After `ours-install`, review `~/fleet.yaml` with the user before activation. Do
|
|
132
|
+
not start Fleet or Telegram merely because installation finished. With explicit
|
|
133
|
+
approval, the exact activation commands are:
|
|
134
|
+
|
|
135
|
+
```sh
|
|
136
|
+
ours-fleet doctor && ours-fleet config && ours-fleet up
|
|
137
|
+
ours-fleet ls
|
|
138
|
+
ours-tg-connector install-service
|
|
139
|
+
```
|
|
140
|
+
|
|
141
|
+
For Telegram, first guide bot and route setup locally. Never ask the user to put
|
|
142
|
+
a bot token in chat, a tool argument, or a transcript.
|
|
143
|
+
|
|
124
144
|
## Layer 1 — identities (global)
|
|
125
145
|
|
|
126
146
|
A session must **bind** an identity before it can send or read messages. Binding is
|