monoban 1.3.0 → 1.5.0
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 +39 -0
- package/dist/index.mjs +2605 -133
- package/package.json +4 -4
package/README.md
CHANGED
|
@@ -29,6 +29,7 @@ monoban schedule MON-12 fri # plan it for a day: tomorrow, next week,
|
|
|
29
29
|
monoban start MON-12 # in the repo: check out mon-12-title (from the commit you're on), move it to In progress
|
|
30
30
|
monoban move MON-12 in-progress # columns match loosely: any case, a unique prefix
|
|
31
31
|
monoban move MON-12 --to WEB # to another project (MON-12 becomes WEB-7); add a column to choose it
|
|
32
|
+
monoban move MON-12 todo --if-column-since 2026-10-14T10:00:00Z # only if it's been in its column since then
|
|
32
33
|
monoban done MON-12
|
|
33
34
|
monoban edit MON-12 # title and description in $EDITOR (or --title, -d, no editor)
|
|
34
35
|
monoban tag MON-12 bug ui # untag MON-12 bug takes one off; list --tag bug filters
|
|
@@ -45,6 +46,44 @@ commands there use MON, in any clone of it. Elsewhere, pick the project with `-p
|
|
|
45
46
|
`MONOBAN_PROJECT=MON`; with a single project, that one is used. `monoban unlink` undoes a link.
|
|
46
47
|
Every command takes `--json`. Exit codes: 0 ok, 1 error, 2 usage, 4 not signed in, 5 not found.
|
|
47
48
|
|
|
49
|
+
## Run with orchestrator
|
|
50
|
+
|
|
51
|
+
Start a coding agent on a task from the board, and it works on your own machine:
|
|
52
|
+
|
|
53
|
+
```sh
|
|
54
|
+
monoban runner # in a terminal on the machine with the code: waits for runs (Ctrl-C stops)
|
|
55
|
+
monoban run MON-12 # or from the board: Run with orchestrator (R). In this clone, unless --path
|
|
56
|
+
monoban run MON-12 --agent claude --model opus --pr none --follow
|
|
57
|
+
monoban run MON-12 --agent codex --access network
|
|
58
|
+
monoban runs MON-12 # its runs, newest first
|
|
59
|
+
```
|
|
60
|
+
|
|
61
|
+
The runner checks in with monoban.dev every few seconds (`--interval`), so nothing reaches into your
|
|
62
|
+
machine. A run works in the folder it was given only if that folder is a checkout of the task's project
|
|
63
|
+
(its origin is the linked repository, or `monoban link` was run there), and inside `--allow` folders if you
|
|
64
|
+
set any; `--confirm` asks before each one. The task's run tab shows the steps.
|
|
65
|
+
|
|
66
|
+
It offers the agents installed on the machine (`--agents` limits them); the run's dialog picks one:
|
|
67
|
+
|
|
68
|
+
- [agentpipe](https://github.com/thiagodmont/agentpipe) (`agentpipe run <folder> --from-issue MON-12`) moves
|
|
69
|
+
the task, comments on it and opens the pull request itself.
|
|
70
|
+
- Claude Code (`claude -p`, 2.1.259 or later) runs in auto mode: a classifier reviews each action, and
|
|
71
|
+
anything that would need a person is refused instead of waiting. `--budget` and `--model` apply.
|
|
72
|
+
- Codex (`codex exec`) runs in its sandbox, writing only in the folder with the network off;
|
|
73
|
+
`--access network` turns the network on and `--access full` turns the sandbox off, but only on a runner
|
|
74
|
+
that allows it (`monoban runner --allow-full-access`, or `"codex": {"allowFullAccess": true}` in
|
|
75
|
+
`runner.json`); elsewhere it stays in the sandbox and the run says so. `--model` applies.
|
|
76
|
+
|
|
77
|
+
For Claude Code and Codex the runner does the rest: the folder must have no uncommitted changes, it makes
|
|
78
|
+
the task's branch (`mon-12-title`) from the up-to-date default branch and moves the task to In progress;
|
|
79
|
+
afterwards it commits what the agent left, pushes, opens the pull request with `gh`, attaches it to the task
|
|
80
|
+
and comments with the agent's summary. A run that fails or is cancelled keeps its work on the branch; one
|
|
81
|
+
that gets stuck ends as "needs you", with its question on the task.
|
|
82
|
+
|
|
83
|
+
Settings can also go in `runner.json` in the config folder: `{"agents": ["claude"], "adapters": {"claude":
|
|
84
|
+
{"command": "/opt/bin/claude", "args": ["--permission-mode", "acceptEdits"]}}}` (the `args` go after the
|
|
85
|
+
runner's own). `$MONOBAN_AGENTPIPE`, `$MONOBAN_CLAUDE` and `$MONOBAN_CODEX` set the commands too.
|
|
86
|
+
|
|
48
87
|
## Coding agents
|
|
49
88
|
|
|
50
89
|
```sh
|