monoban 1.4.0 → 1.5.1

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.
Files changed (3) hide show
  1. package/README.md +52 -47
  2. package/dist/index.mjs +2597 -135
  3. package/package.json +10 -6
package/README.md CHANGED
@@ -1,62 +1,67 @@
1
+ <p align="center">
2
+ <a href="https://monoban.dev"><img src="https://monoban.dev/og.png" alt="monoban: your tasks, one keystroke away" width="760"></a>
3
+ </p>
4
+
1
5
  # monoban
2
6
 
3
- The command line for [monoban.dev](https://monoban.dev), a keyboard-first kanban board.
7
+ Your [monoban.dev](https://monoban.dev) board, in your terminal. Add, move and start tasks without leaving
8
+ the repository you're working in, script it with `--json`, and hand tasks to coding agents.
4
9
 
5
10
  ```sh
6
- npx monoban login # approve in your browser
7
- monoban whoami
8
- monoban logout
11
+ brew install thiagodmont/tap/monoban # macOS and Linux: a standalone binary, completions included
12
+ npm install -g monoban # or npx monoban, with Node 22.12+
9
13
  ```
10
14
 
11
- Signing in opens monoban.dev/panel and asks you to authorize this computer. Over SSH, or anywhere
12
- without a browser, `monoban login --device` shows a code to approve at monoban.dev/panel/device on any
13
- device. The sign-in is kept in your system keychain, and you can sign CLIs out in monoban.dev/panel →
14
- Devices & tokens.
15
+ ## Quick start
15
16
 
16
17
  ```sh
17
- monoban projects # your projects and their keys
18
- monoban list # the board, by column (or: monoban ls backlog doing)
19
- monoban list --archived # tasks done long ago, off the board (after 14 days in Done, by default)
20
- monoban add "Write the docs" -c todo # -d "text", -d - (stdin) or -e ($EDITOR) for a description
21
- monoban add "Fix login" -t bug # -t tags it (repeat for more; a new name makes a tag); --date fri plans it
22
- monoban show MON-12
23
- monoban log MON-12 # what happened to it, newest first (-n 50 for more)
24
- monoban comment MON-12 "Started on it" # a comment, in Markdown; - reads it from stdin
25
- monoban comments MON-12 # its latest comments, oldest of them first (-n for how many)
26
- monoban today # what's planned for today in every project, overdue first (or: today fri --week)
27
- monoban search login bug # tasks with all the words, in every project (title, description, tag, MON-12)
28
- monoban schedule MON-12 fri # plan it for a day: tomorrow, next week, +3, oct 12… (--clear takes it off)
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
- monoban move MON-12 in-progress # columns match loosely: any case, a unique prefix
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
33
- monoban done MON-12
34
- monoban edit MON-12 # title and description in $EDITOR (or --title, -d, no editor)
35
- monoban tag MON-12 bug ui # untag MON-12 bug takes one off; list --tag bug filters
36
- monoban tags # the project's tags, and the shared ones
37
- monoban notes # the project's notes; notes edit ($EDITOR), notes add "a line"
38
- monoban attach --pr # this branch's pull request (via gh) on the task it's named after (mon-12-…)
39
- monoban attach MON-12 https://… # any link; again refreshes it. detach MON-12 #54 takes it off
40
- monoban rm MON-12
41
- monoban open MON-12 # in the browser
18
+ monoban login # approve in your browser (--device for a code, over SSH)
19
+ monoban link SHOP # in your clone: commands here use project SHOP from now on
20
+
21
+ monoban add "Fix the flaky checkout test" -t bug
22
+ monoban list # the board, column by column
23
+ monoban start SHOP-14 # check out shop-14-fix-the-flaky-checkout-test, move it to In progress
24
+ monoban attach --pr # this branch's pull request, on its task (with gh)
25
+ monoban done SHOP-14
42
26
  ```
43
27
 
44
- In a clone of your repository, `monoban link MON` links project MON to it (its GitHub origin): from then on
45
- commands there use MON, in any clone of it. Elsewhere, pick the project with `-p MON` or
46
- `MONOBAN_PROJECT=MON`; with a single project, that one is used. `monoban unlink` undoes a link.
47
- Every command takes `--json`. Exit codes: 0 ok, 1 error, 2 usage, 4 not signed in, 5 not found.
28
+ ## What it does
29
+
30
+ | | |
31
+ |---|---|
32
+ | **The board** | `list` · `add` · `show` · `move` · `done` · `edit` · `rm` · `tag` · `notes` · `open` |
33
+ | **Across projects** | `today` (what's planned, overdue first) · `search` · `schedule SHOP-14 fri` · `move --to` |
34
+ | **Your repository** | `link` · `start` (branch + In progress) · `attach --pr` |
35
+ | **History** | `log` (what happened to a task) · `comment` · `comments` |
36
+ | **Coding agents** | `setup claude` · `setup codex` · `runner` · `run` · `runs` |
37
+
38
+ `monoban <command> --help` says more. Columns match loosely (`move SHOP-14 in-prog`), and Tab completes
39
+ commands, projects, columns and tasks (`monoban completion zsh`).
48
40
 
49
41
  ## Coding agents
50
42
 
51
- ```sh
52
- monoban setup claude # Claude Code: ~/.claude/skills/monoban
53
- monoban setup codex # Codex: ~/.agents/skills/monoban
54
- ```
43
+ **Teach yours the board.** `monoban setup claude` (or `codex`) installs a skill: when the agent plans work,
44
+ it offers to put the plan on your board as tasks, then keeps them current as it goes.
45
+
46
+ **Or let one do the task.** Run `monoban runner` on the machine with the code, then press `R` on a task at
47
+ monoban.dev (or `monoban run SHOP-14 --agent claude --follow`). The runner works in your clone: it makes
48
+ the task's branch, runs Claude Code, Codex or agentpipe, then pushes and opens the pull request. The task
49
+ shows each step as it happens.
50
+
51
+ - The runner only asks monoban.dev for work: nothing reaches into your machine.
52
+ - It works only in a clone of the task's project (for Claude Code and Codex, one with no uncommitted
53
+ changes), and `--confirm` asks before each run.
54
+ - Claude Code runs in auto mode (a classifier reviews each action). Codex runs in its sandbox, with the
55
+ network only when a run asks; without the sandbox only on a runner started with `--allow-full-access`.
56
+
57
+ ## Scripts and CI
58
+
59
+ Every command takes `--json`, results go to stdout and messages to stderr. Exit codes: `0` ok, `1` error,
60
+ `2` usage, `4` not signed in, `5` not found. In CI, sign in with a personal access token (made at
61
+ monoban.dev → Settings): `MONOBAN_TOKEN`, or `monoban login --with-token < file`. `MONOBAN_PROJECT` or
62
+ `-p SHOP` picks the project anywhere.
55
63
 
56
- This installs a skill that teaches the agent monoban. When it plans work, it offers to add the plan to
57
- your board: one task per step, tagged `phase-1`, `phase-2`… by phase. It creates them only once you agree,
58
- and keeps them current as it works. `--project` installs the skill in the repository instead (to commit
59
- it for everyone), `--print` shows it, and `--remove` takes it out. Run `setup` again after upgrading
60
- monoban. Claude may run the commands that only read (`list`, `show`, `tags`…) without asking.
64
+ Your sign-in is kept in the system keychain, and each new one is emailed to you. Sign out any computer at
65
+ monoban.dev → Settings.
61
66
 
62
- Needs Node 22.12 or newer.
67
+ MIT