runspur 0.1.1 → 0.1.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/README.md CHANGED
@@ -1,35 +1,38 @@
1
1
  # Runspur CLI
2
2
 
3
- Runspur lets Codex and Claude Code delegate work to each other and sends results back to the conversation that started the task. This npm package contains the Windows x64 daemon, CLI, and MCP bridge as native executables.
3
+ Runspur lets Codex and Claude Code delegate work to each other and sends results back to the conversation that started the task. The Windows x64 npm package includes the Runspur CLI, scheduler, MCP bridge, and local browser panel.
4
4
 
5
5
  ## Install
6
6
 
7
7
  With Node.js and npm installed, run the following in PowerShell.
8
8
 
9
9
  ```powershell
10
- npm.cmd install --global runspur
11
- schedulerd.cmd --version
12
- schedulerctl.cmd --help
13
- scheduler-mcp.cmd --help
10
+ npm install --global runspur
11
+ runspur --version
14
12
  ```
15
13
 
16
- ## Connect a project
14
+ If PowerShell blocks script shims, use `npm.cmd` and `runspur.cmd`.
17
15
 
18
- Start `schedulerd.cmd` in one terminal and keep it running. In another terminal, point the CLI at an existing project folder. Review the first command's preview, then save with `--apply`.
16
+ ## Open the panel
17
+
18
+ Run the following to open the panel in your browser. Runspur starts the local scheduler as needed.
19
19
 
20
20
  ```powershell
21
- $project = 'D:\path\your-project'
22
- schedulerctl.cmd configure --project-root $project --main-agent codex
23
- schedulerctl.cmd configure --project-root $project --main-agent codex --apply
24
- schedulerctl.cmd doctor --project-root $project
21
+ runspur tui
25
22
  ```
26
23
 
27
- Open a new conversation in the configured host so it can discover the Skill and MCP tools. Automatic result delivery is verified on the supported Codex desktop distribution and on native Claude Code CLI sessions. Claude Code requires version 2.1.319 or later. Claude Desktop is untested.
24
+ In **Projects**, add an existing folder and select the main Agent, child Agents, and file permissions. Review the configuration and confirm to connect the project. Open a new conversation in the configured host to load the project's Skill and MCP tools.
25
+
26
+ Automatic result delivery is verified on the supported Codex desktop distribution and on native Claude Code CLI sessions. Claude Code requires version 2.1.319 or later. Claude Desktop is untested.
27
+
28
+ For headless use, run `runspur start` to start the scheduler in the background and `runspur stop` to stop it. Each command returns when the scheduler reaches the requested state.
29
+
30
+ ## Manage projects and dispatches
28
31
 
29
- The default `probe` worker is for diagnostics. Set `--workers claude-cli` to use an installed Claude Code worker with a Codex main Agent. To switch roles, use `--main-agent claude-code --workers codex-cli`. Worker access starts read-only. With a supported Claude Code worker, use `--permission workspace-write` for task-specific files or `--permission project-write` for text files across the isolated project workspace. Preview and apply edits with `configure`.
32
+ Use **Projects** to edit the Agents or permissions of a connected project. Worker access defaults to read-only. Use Claude Code **2.1.319** for workers that need permission to edit task-specific files or text files across the isolated project workspace.
30
33
 
31
- Use `schedulerctl.cmd projects`, `sessions --project <project-id>`, and `tasks --project <project-id>` to locate a dispatch. Use `schedulerctl.cmd task <task-id>` to inspect its result and delivery status.
34
+ Use **Dispatch history** to find tasks by project and conversation, then inspect their results and delivery status.
32
35
 
33
- Stop the Runspur processes before updating with `npm.cmd update --global runspur` or removing the package with `npm.cmd uninstall --global runspur`. Project settings and the Runspur state directory are stored separately.
36
+ Before uninstalling, finish active tasks and close connected Agent conversations. Stop the scheduler from **Overview** or run `runspur stop`. If the panel is open, press Ctrl+C in the `runspur tui` terminal to close it. Then run `npm uninstall --global runspur`. Project settings and the Runspur state directory are stored separately.
34
37
 
35
38
  [Full usage and source](https://github.com/ohmacemace/runspur) · [简体中文](https://github.com/ohmacemace/runspur/blob/main/docs/README.zh-CN.md)