@kaiba-cloud/orbital 0.0.3 → 0.0.5

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,6 +1,6 @@
1
1
  # Orbital
2
2
 
3
- Orbital runs teams of agents on your machine. A team has a lead and members. You give the team a mission, and you watch it live in your terminal or in Claude Code.
3
+ Orbital is a harness runner for agent harnesses. It lets agents on different harnesses (Claude Code, Codex, Pi or your own) work as one team and talk to each other. You use it to build agent factories.
4
4
 
5
5
  ## Install
6
6
 
@@ -18,6 +18,20 @@ Orbital runs teams of agents on your machine. A team has a lead and members. You
18
18
 
19
19
  3. In Claude Code, run `/reload-plugins`, then `/orbital` to open the pane.
20
20
 
21
+ ## Update the Claude Code mod
22
+
23
+ The Claude adapter owns the mod. `orbital install claude` writes the mod when it is missing and refreshes it when it is old. It writes only the files that changed and reports each change. If nothing changed, it writes nothing.
24
+
25
+ 1. After you update orbital, run the install again in your repository.
26
+
27
+ ```bash
28
+ orbital install claude
29
+ ```
30
+
31
+ 2. In Claude Code, run `/reload-plugins`.
32
+
33
+ Codex and Pi have no mod. `orbital install codex` and `orbital install pi` connect those harnesses the same way, and a second run writes nothing.
34
+
21
35
  ## Skills
22
36
 
23
37
  - The orbital-team skill comes with the mod. It teaches Claude to work with teams and missions.
@@ -88,8 +102,10 @@ Paste this prompt into Claude Code in your repository:
88
102
 
89
103
  ## Keep it running
90
104
 
91
- Each node runs in the background under a supervisor. Closing the view (`q`, Ctrl+C or a closed terminal) stops no node. Only `orbital down` stops the nodes.
105
+ Each node runs in the background under a supervisor. Closing the view (`q`, Ctrl+C or a closed terminal) stops no node. To stop a node, use the keys of the view or `orbital down`.
92
106
 
107
+ - In the view, `S` stops the selected node and `R` restarts it on the installed orbital, so it picks up a new version. `Q` stops every node of the view and closes the view. Each key asks for `y` first.
108
+ - A restart keeps the work going: a mission that was active or waiting before the restart goes on by itself.
93
109
  - If a node crashes, its supervisor starts it again and the view says why. A mission that was active comes back paused. Resume it with `orbital mission resume <id>`.
94
110
  - A second `orbital up` shows the nodes that run. `orbital up --new` starts a separate node for a separate run, such as `<node>-2`.
95
111
  - To start the nodes at each login, install the login service. It uses launchd on macOS and systemd on Linux, and it needs no sudo.
@@ -116,6 +132,14 @@ Each agent session that starts its own chrome-devtools server makes Chrome ask y
116
132
  orbital browser install --revert
117
133
  ```
118
134
 
135
+ ## Plugins
136
+
137
+ A plugin adds ports to a node, and it can add commands to this CLI.
138
+ `orbital plugin add <source>` names a plugin in `orbital.yaml`.
139
+ A plugin `acme` that declares a `login` command runs with `orbital acme login`.
140
+ `orbital help` lists the commands of each plugin, and a built-in command always wins.
141
+ To write a plugin, use the plugin builder skill and `orbital plugin new`.
142
+
119
143
  ## Commands
120
144
 
121
145
  | Command | What it does |