@ouro.bot/cli 0.1.0-alpha.362 → 0.1.0-alpha.363

package/README.md

@@ -169,6 +169,7 @@ ouro auth --agent <name>
 ouro auth --agent <name> --provider <provider>
 ouro use --agent <name> --lane <outward|inner> --provider <provider> --model <model>
 ouro hatch
+ouro clone <remote> [--agent <name>]   # clone an existing agent from a git remote (see docs/cross-machine-setup.md)
 ouro chat <agent>
 ouro msg --to <agent> [--session <id>] [--task <ref>] <message>
 ouro poke <agent> --task <task-id>
@@ -183,6 +184,10 @@ ouro mcp-serve --agent <name>             # start MCP server on stdin/stdout (us
 ouro hook <event> --agent <name>          # fire a lifecycle hook (SessionStart, Stop, PostToolUse)
 ```
 
+## Setting Up On Another Machine
+
+To clone an existing agent onto a new machine (macOS, Linux, or Windows via WSL2), see **[docs/cross-machine-setup.md](docs/cross-machine-setup.md)**. The short version: `npx ouro.bot`, pick "clone", enter the bundle's git remote URL, run `ouro auth run`, then `ouro up`.
+
 ## The Agent's Inner Life
 
 Agents in Ouroboros aren't just responders — they have an autonomous inner life.

package/changelog.json

@@ -1,6 +1,12 @@
 {
   "_note": "This changelog is maintained as part of the PR/version-bump workflow. Agent-curated, not auto-generated. Agents read this file directly via read_file to understand what changed between versions.",
   "versions": [
+    {
+      "version": "0.1.0-alpha.363",
+      "changes": [
+        "Bootstrap first-install PATH hint is now shell-aware: shows correct source command for zsh, bash, fish, or generic fallback for unknown shells."
+      ]
+    },
     {
       "version": "0.1.0-alpha.362",
       "changes": [

package/dist/mind/prompt.js

@@ -382,6 +382,7 @@ function runtimeInfoSection(channel, options) {
     lines.push(`process type: ${processTypeLabel(channel)}`);
     lines.push(`daemon: ${daemonStatus(options?.daemonRunning)}`);
     lines.push(`mcp serve: i can expose my tools to dev tools via \`ouro mcp-serve\`. see the configure-dev-tools skill for setup.`);
+    lines.push(`harness docs: the harness repo has docs/ and skills/ with guides for setup, operations, and capabilities. docs/ does NOT ship in the npm package — in production, fetch from https://github.com/ouroborosbot/ouroboros/tree/main/docs instead. in dev mode, read from ${sourceRoot}/docs/. when someone asks about setup, installation, cross-machine cloning, deployment, testing, auth, or how i work — consult the docs before guessing.`);
     if (channel === "cli") {
         lines.push("i introduce myself on boot with a fun random greeting.");
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ouro.bot/cli",
-  "version": "0.1.0-alpha.362",
+  "version": "0.1.0-alpha.363",
   "main": "dist/heart/daemon/ouro-entry.js",
   "bin": {
     "cli": "dist/heart/daemon/ouro-bot-entry.js",

package/skills/configure-dev-tools.md

@@ -1,6 +1,6 @@
 # Configure Dev Tools for MCP Agent Bridge
 
-Set up your development tools (Claude Code, Codex) to communicate with Ouroboros agents via MCP. One command does everything.
+Set up your development tools (Claude Code, Codex) to communicate with Ouroboros agents via MCP. One command does everything — including cross-platform WSL2 bridging on Windows.
 
 ## Setup
 
@@ -15,6 +15,16 @@ This command:
 2. Configures lifecycle hooks (SessionStart, Stop, PostToolUse) for passive awareness
 3. Detects dev vs installed mode automatically and uses the correct command path
 
+**On WSL2 (Windows):** The command automatically detects the WSL environment and:
+- Calls `claude.exe` (the Windows binary) instead of `claude`
+- Prefixes MCP serve and hook commands with `wsl` so Windows-side Claude Code spawns them through WSL
+- Resolves the Windows-side home directory and writes config to the Windows-side `~/.claude/`
+- After setup, open Claude Code in PowerShell — the agent is there
+
+**On native Windows (no WSL):** Not yet supported. The command prints a message directing you to install WSL2.
+
+For the full cross-machine setup flow (including cloning an agent to a new machine), see `docs/cross-machine-setup.md` in the harness repo.
+
 ### Codex
 
 ```bash