agenticros 0.3.0 → 0.3.1

package/runtime/README.md

@@ -27,7 +27,7 @@ With AgenticROS, your robot can describe what it sees, follow intent ("go check
 - **[OpenClaw](https://openclaw.ai)** — Native gateway plugin with ROS 2 tools, commands, a config UI, a teleop web app, and a skill loader. The flagship integration.
 - **[NVIDIA NemoClaw](https://github.com/NVIDIA/NemoClaw)** — Run AgenticROS inside NemoClaw's OpenShell sandbox with policy-enforced egress and managed NVIDIA inference; ROS 2, RealSense, and rosbridge stay on the host while the plugin runs sandboxed.
 - **[Anthropic Claude](https://www.anthropic.com/claude)** — A single MCP server powers **Claude Code** (terminal), **Claude Desktop** (macOS / Windows), and **Claude Dispatch** (iOS, paired to your Mac). Ask Claude what your robot sees, and it answers with a live camera snapshot and depth reading.
-- **[OpenAI Codex CLI](https://developers.openai.com/codex/)** — The same MCP server registers cleanly via `codex mcp add agenticros — node …/packages/agenticros-claude-code/dist/index.js`, or via a `[mcp_servers.agenticros]` entry in `~/.codex/config.toml`. Same 15 tools, same JSON shapes. Setup: [packages/agenticros-claude-code/README.md#codex-cli-openai](packages/agenticros-claude-code/README.md#codex-cli-openai).
+- **[OpenAI Codex CLI](https://developers.openai.com/codex/)** — Same MCP server as Claude Code. One command registers Codex: `agenticros codex setup` (writes `~/.codex/config.toml` with an absolute path to the MCP binary). Full tool surface: missions, follow-me, find-object, memory. Setup guide: [docs/codex-setup.md](docs/codex-setup.md).
 - **[Google Gemini](https://ai.google.dev/)** — Standalone CLI that uses Gemini function calling against the same ROS 2 tools (no MCP required) — ideal for scripting and headless agents.
 
 AgenticROS is built so that new adapters (LangGraph, OpenAI, local models, voice stacks, etc.) can be added without touching the ROS 2 layer. The core transport and tool contract are platform-agnostic; adapters are thin shims that surface those tools to each agent runtime.
@@ -38,12 +38,13 @@ AgenticROS is built so that new adapters (LangGraph, OpenAI, local models, voice
 
 - **Core** (`packages/core`): Platform-agnostic ROS2 transport (rosbridge, Zenoh, local, WebRTC), config schema, and shared types. No dependency on any specific AI platform.
 - **Adapters** (`packages/agenticros`, and later others): Implement the contract for each AI platform. The OpenClaw adapter registers tools, commands, and HTTP routes with the OpenClaw gateway and uses the core for all ROS2 communication.
-- `**packages/agenticros-claude-code`** — MCP server for **Claude Code** (terminal), **Claude desktop** (macOS), and **Dispatch** (iOS paired to Mac). See [packages/agenticros-claude-code/README.md](packages/agenticros-claude-code/README.md).
+- `**packages/agenticros-claude-code`** — MCP server for **Claude Code**, **Claude desktop**, **Dispatch**, and **OpenAI Codex CLI**. See [packages/agenticros-claude-code/README.md](packages/agenticros-claude-code/README.md) and [docs/codex-setup.md](docs/codex-setup.md).
 - `**packages/agenticros-gemini`** — **Gemini CLI**: use Google Gemini to chat with your robot from the terminal (same ROS2 tools, no MCP). See [packages/agenticros-gemini/README.md](packages/agenticros-gemini/README.md).
 
 ```
 User (messaging app) → OpenClaw Gateway → AgenticROS OpenClaw plugin → Core → ROS2 robots
 Claude (Code / desktop / Dispatch) → agenticros MCP server → Core → ROS2 robots (Zenoh/rosbridge)
+Codex CLI → agenticros MCP server → Core → ROS2 robots (Zenoh/rosbridge)
 Gemini CLI → @agenticros/gemini (function calling) → Core → ROS2 robots
 ```
 
@@ -381,13 +382,17 @@ Add `{ "memory": { "enabled": true, "backend": "mem0" } }` to `~/.agenticros/con
 
 ## Skills
 
-AgenticROS **skills** are optional packages that add tools and behaviors to the plugin (e.g. `follow_robot`, `find_object`). They are loaded at OpenClaw gateway start. **[AgenticROS Skills](https://github.com/agenticros/agenticros-skills)** is a curated list — use it to discover skills for your robot and to submit your own.
+AgenticROS **skills** are optional packages that add tools and behaviors to the plugin (e.g. `follow_person`, `find_object`). They are loaded at OpenClaw gateway start. Browse and install from **[skills.agenticros.com](https://skills.agenticros.com)**, or scaffold and publish your own with the CLI.
 
 ### Managing skills with the CLI
 
 The `agenticros skills` command (and the **Manage skills** menu entry) does everything for you: it scans the usual locations for clones, edits `~/.openclaw/openclaw.json`, refreshes the plugin manifest's `contracts.tools` allowlist, and reminds you to bounce the gateway.
 
 ```bash
+# Install from the marketplace (owner/skill-id ref)
+npx agenticros skills search follow
+npx agenticros skills install chrismatthieu/followme
+
 agenticros skills                       # list registered + cloned-but-unregistered
 agenticros skills discover              # interactive picker over candidates on disk
 agenticros skills add <path-or-name>    # register a clone (path) or npm package
@@ -395,7 +400,15 @@ agenticros skills remove <id-or-name>   # unregister
 agenticros skills sync                  # refresh OpenClaw contracts.tools allowlist
 ```
 
-A typical first-run looks like:
+**Create and publish** a new skill:
+
+```bash
+npx agenticros create-skill my-skill --template robot
+cd agenticros-skill-my-skill && npm install && npm run dev
+npx agenticros publish
+```
+
+A typical manual install (without the marketplace) looks like:
 
 ```bash
 # clone whichever skills you want, anywhere near the repo
@@ -441,7 +454,7 @@ Per-skill behaviour lives under `config.skills.<skillId>` (e.g. `config.skills.f
 
 ### Contract & writing your own skill
 
-A skill is a Node package with an `"agenticros": { "id": "..." }` block in `package.json` and a `registerSkill(api, config, context)` export from `main`. Publish it to **[skills.agenticros.com](https://skills.agenticros.com)** so others can install it with `npx agenticros skills install <slug>`. See **[docs/skills.md](docs/skills.md)** for the full contract and **[agenticros-skill-followme](https://github.com/agenticros/agenticros-skill-followme)** as a reference template.
+A skill is a Node package with an `"agenticros": { "id": "..." }` block in `package.json` and a `registerSkill(api, config, context)` export from `main`. Scaffold with `npx agenticros create-skill`, publish to **[skills.agenticros.com](https://skills.agenticros.com)** with `npx agenticros publish`, and install with `npx agenticros skills install <owner/skill-id>` (e.g. `chrismatthieu/followme`). See **[docs/skills.md](docs/skills.md)** for the full contract and **[agenticros-skill-followme](https://github.com/agenticros/agenticros-skill-followme)** ([marketplace listing](https://skills.agenticros.com/chrismatthieu/followme)) as a reference template.
 
 ## Strategy & vision
 

package/runtime/docs/cli.md

@@ -134,7 +134,7 @@ Read or edit `~/.agenticros/config.json`. Actions:
 | `agenticros create-skill <slug> [--template hello\|robot\|camera\|depth]` | Scaffold `./agenticros-skill-<slug>/` in cwd. |
 | `agenticros skills dev [--invoke <tool>] [--live]` | Load the skill locally without OpenClaw. |
 | `agenticros publish [--graduate]` | Validate, push to GitHub, submit to skills.agenticros.com. |
-| `agenticros skills install <owner/skill>` | Install from marketplace (e.g. `agenticros/followme`). |
+| `agenticros skills install <owner/skill>` | Install from marketplace (e.g. `chrismatthieu/followme`). |
 | `agenticros skills search <q>` | Search the marketplace. |
 
 ## Troubleshooting

package/runtime/packages/agenticros-claude-code/README.md

@@ -96,9 +96,19 @@ Scope options: `--scope user` (default), `--scope project` (shared via `.mcp.jso
 
 ## Codex CLI (OpenAI)
 
-The same MCP server works unmodified with the **OpenAI Codex CLI** — Codex is a vanilla MCP client, and our server speaks the standard `2024-11-05` MCP protocol that every MCP-compatible client uses. Two ways to register it:
+The same MCP server works unmodified with the **OpenAI Codex CLI** — Codex is a vanilla MCP client, and our server speaks the standard MCP protocol.
 
-**Option A — `codex mcp add` (recommended)**
+**Option A — `agenticros codex setup` (recommended)**
+
+```bash
+agenticros codex setup              # ~/.codex/config.toml
+agenticros codex setup --project    # .codex/config.toml in repo root
+agenticros codex doctor
+```
+
+Then start Codex and run `/mcp` — you should see `agenticros` connected. See [docs/codex-setup.md](../../docs/codex-setup.md) for the full guide.
+
+**Option B — `codex mcp add`**
 
 ```bash
 cd /path/to/agenticros
@@ -106,20 +116,20 @@ codex mcp add agenticros \
   -- node "$(pwd)/packages/agenticros-claude-code/dist/index.js"
 ```
 
-**Option B — direct edit of `~/.codex/config.toml`**
+**Option C — direct edit of `~/.codex/config.toml`**
 
 ```toml
 [mcp_servers.agenticros]
-command = "node"
-args = ["/ABSOLUTE/PATH/TO/agenticros/packages/agenticros-claude-code/dist/index.js"]
+command = "sh"
+args = ["-c", "node /ABSOLUTE/PATH/TO/agenticros/packages/agenticros-claude-code/dist/index.js 2>>/tmp/agenticros-mcp.log"]
 enabled = true
 startup_timeout_sec = 30
 
 [mcp_servers.agenticros.env]
-AGENTICROS_ROBOT_NAMESPACE = "robotYOUR_NAMESPACE_NO_DASHES"
+AGENTICROS_ROBOT_NAMESPACE = ""
 ```
 
-Then start a Codex session and run `/mcp` to verify — you should see `agenticros` connected with **15 tools** (more if you have skills like `agenticros-skill-followme` or `agenticros-skill-find` registered). Same tools, same tool names, same JSON shapes as in Claude Code; everything in the **Tools** section below applies identically.
+Same tools, same tool names, same JSON shapes as in Claude Code; everything in the **Tools** section below applies identically.
 
 Two Codex-specific notes:
 
@@ -300,4 +310,4 @@ If `ros2_publish` runs but the robot doesn’t move:
 
 ## Skills
 
-Skill packages (e.g. `agenticros-skill-followme`, `agenticros-skill-find`) extend the capability registry with new verbs like `follow_person` and `find_object`. The MCP server reads each skill's `package.json` `agenticros` block (`id`, `capabilities[]`) at startup and surfaces those verbs through `ros2_list_capabilities` and `run_mission` — no per-skill MCP tool needed. To register a skill for this adapter, install it with `agenticros skills install <slug>` from the marketplace, or add its path under `skillPaths[]` in `~/.agenticros/config.json` (or use the `agenticros skills add <path>` CLI). See [docs/skills.md](../../docs/skills.md) for the full skill contract.
+Skill packages (e.g. `agenticros-skill-followme`, `agenticros-skill-find`) extend the capability registry with new verbs like `follow_person` and `find_object`. The MCP server reads each skill's `package.json` `agenticros` block (`id`, `capabilities[]`) at startup and surfaces those verbs through `ros2_list_capabilities` and `run_mission` — no per-skill MCP tool needed. To register a skill for this adapter, install it with `agenticros skills install <owner/skill-id>` from the marketplace (e.g. `chrismatthieu/followme`), or add its path under `skillPaths[]` in `~/.agenticros/config.json` (or use the `agenticros skills add <path>` CLI). See [docs/skills.md](../../docs/skills.md) for the full skill contract.

package/runtime/packages/agenticros-claude-code/package.json

@@ -2,7 +2,17 @@
   "name": "@agenticros/claude-code",
   "version": "0.0.1",
   "type": "module",
-  "description": "AgenticROS MCP server for Claude Code CLI — chat with your ROS2 robot from the terminal",
+  "description": "AgenticROS MCP server for Claude Code, Claude Desktop, Dispatch, and OpenAI Codex CLI — chat with your ROS2 robot from the terminal",
+  "keywords": [
+    "agenticros",
+    "ros2",
+    "robotics",
+    "mcp",
+    "claude",
+    "codex",
+    "openai",
+    "model-context-protocol"
+  ],
   "main": "./dist/index.js",
   "bin": {
     "agenticros-mcp": "./dist/index.js"

package/runtime/packages/core/README.md

@@ -21,6 +21,16 @@ You don't normally use it directly — you use one of the adapters that depends
 
 A skill is an npm package that registers tools the AI agent can call on your robot.
 
+**Quick start** — scaffold, dev locally, publish:
+
+```bash
+npx agenticros create-skill my-skill
+cd agenticros-skill-my-skill && npm install && npm run dev
+npx agenticros publish
+```
+
+Or start from scratch with `@agenticros/core`:
+
 ```bash
 npm install --save @agenticros/core
 ```
@@ -75,10 +85,10 @@ export const registerSkill: RegisterSkill = (api, _config, _context) => {
 };
 ```
 
-Submit your skill to the marketplace at **[skills.agenticros.com/submit](https://skills.agenticros.com/submit)** — sign in with GitHub, paste your repo URL, and your skill becomes installable with:
+Publish to the marketplace with `npx agenticros publish`, or submit via **[skills.agenticros.com/submit](https://skills.agenticros.com/submit)**. Published skills use namespaced refs `owner/skill-id` (your GitHub login + `agenticros.id`):
 
 ```bash
-npx agenticros skills install myskill
+npx agenticros skills install your-handle/myskill
 ```
 
 See the [skills contract & guide](https://github.com/agenticros/agenticros/blob/main/docs/skills.md) for the full reference.