@zetaloop/chappie 0.4.1 → 1.0.0

package/.codex-plugin/plugin.json

@@ -0,0 +1,13 @@
+{
+	"name": "chappie",
+	"description": "Connect ChatGPT and local agents across devices",
+	"mcpServers": {
+		"chappie": {
+			"command": "node",
+			"args": ["dist/cli.js", "codex"],
+			"env_vars": ["CODEX_HOME"],
+			"cwd": "."
+		}
+	},
+	"version": "1.0.0"
+}

package/README.md

@@ -1,62 +1,53 @@
 # Chappie
 
-Use ChatGPT to work through [Pi](https://github.com/earendil-works/pi): edit local files, run commands, call Pi extensions, exchange files and images, and move between sessions on one or more devices.
+Use ChatGPT to work through Pi, Oh My Pi, OpenCode, or Codex: edit projects, run commands, and exchange files and images. Agent sessions can also work with each other, on the same computer or across devices.
 
 ## Setup
 
-Install the Pi package:
+Install Chappie in each participating agent:
+
+| Agent                                             | Install                                          |
+| ------------------------------------------------- | ------------------------------------------------ |
+| [Pi](https://github.com/earendil-works/pi)        | `pi install npm:@zetaloop/chappie`               |
+| [Oh My Pi](https://github.com/can1357/oh-my-pi)   | `omp plugin install @zetaloop/chappie`           |
+| [OpenCode](https://github.com/anomalyco/opencode) | `opencode plugin add @zetaloop/chappie`          |
+| [Codex](https://github.com/openai/codex)          | [Plugin and provider setup](docs/setup.md#codex) |
+
+The broker connects these sessions to ChatGPT and to each other. Install it on one device:
 
 ```sh
-pi install npm:@zetaloop/chappie
+pnpm add -g @zetaloop/chappie
 ```
 
-Run Chappie as the MCP server managed by [otunnel](https://github.com/zetaloop/otunnel):
+## With ChatGPT
+
+Run the broker through [otunnel](https://github.com/zetaloop/otunnel) with this MCP configuration:
 
 ```yaml
 mcp:
   commands:
     - channel: main
-      command: pi --chappie
-```
-
-Add the tunnel as a developer-mode app in ChatGPT, then start Pi in a project:
-
-```sh
-pi --provider chappie --model chatgpt
+      command: chappie
 ```
 
-Call `init` from ChatGPT to connect the conversation to Pi. A conversation can resume an existing task with its Pi session ID, while `sessions` can find connected sessions by device, directory, or name.
-
-## Usage
+Add the tunnel as a developer-mode app in ChatGPT. Open a project in the agent with its Chappie model selected, then tell ChatGPT which project or session to use and what to do:
 
-Chappie exposes common coding tools directly and every active Pi tool through `tools` and `call`. `chat` sends an assistant message to Pi, Pi input accompanies later tool results, and `transfer` moves files in either direction. `history` reads recent Pi messages and activity with timestamps. `ask` can present a persistent question in ChatGPT when webpage questions are enabled.
+> Use \@Chappie to review the recent changes in the website project.
 
-See the [tool guide](docs/tools.md) for session selection, history, synchronization, Pi tools, webpage questions, and file transfer.
+Tool activity and assistant messages appear in the agent's interface. Messages entered there reach ChatGPT with later tool results. Attach files in ChatGPT for the agent to use, or ask for generated files to be sent back.
 
-## Configuration
+To continue from another chat or branch, ask ChatGPT to reconnect to the same agent session.
 
-`chappie.json` in Pi's agent directory configures Chappie.
+## Between agents
 
-A broker can accept Pi sessions from other devices on the local network:
+An agent using its usual model can work through another agent session. For example, an assistant on macOS can run a build in a Windows session and retrieve the output files.
 
-```json
-{ "listen": true }
-```
-
-Remote Pi sessions connect through the broker device's mDNS name:
+Start `chappie` in a terminal, or use the broker already running through otunnel. On the controlling agent's device, enable local tools in `~/.chappie/config.json`:
 
 ```json
-{ "connect": "<broker>.local" }
+{ "localTools": true }
 ```
 
-The default port is `24274`. Set `listen` to a port number or append `:port` to `connect` to use another one. Only the broker device runs otunnel; local and remote sessions appear in the same session list.
-
-Set `ask` to `false` to disable webpage questions.
-
-Enable synchronization to resolve conflicting activity:
-
-```json
-{ "sync": true }
-```
+Use the usual model in the controlling session and the Chappie model in the target session. Ask the controlling assistant to find that session and work on its project.
 
-Initialization returns a short name and a private code. `sync` pauses conflicting work for discussion through `chat` and `history`. The verified coordinator decides who continues, their tasks, and who exits, including retaining only one execution. See [synchronization](docs/tools.md#synchronization).
+See [setup and configuration](docs/setup.md) for device connections and agent-specific settings, and the [tool guide](docs/tools.md) for the available operations and their parameters.