rumo-cli 0.3.0__tar.gz → 0.5.0__tar.gz

{rumo_cli-0.3.0 → rumo_cli-0.5.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: rumo-cli
-Version: 0.3.0
+Version: 0.5.0
 Summary: Your dev work, past, now and later: Markdown files, a terminal Timeline, and AI agents that keep it current
 Project-URL: Homepage, https://github.com/pedrobuzzi/rumo
 Project-URL: Issues, https://github.com/pedrobuzzi/rumo/issues
@@ -63,6 +63,10 @@ system language.
   /plugin install rumo@rumo
   ```
 
+  `/rumo` runs its `rumo` commands without asking. To let the agent run them without asking in later
+  answers too (to link an item it offered to create, for example), add `"Bash(rumo:*)"` to
+  `permissions.allow` in `~/.claude/settings.json`.
+
 - **Codex, Gemini CLI, Cursor, GitHub Copilot and other agents** that read `SKILL.md` files,
   simple mode (create items and ideas, list and search them; no automatic updates):
 
@@ -85,7 +89,7 @@ To get new plugin versions on their own, turn on auto-update for the `rumo` mark
 | Key | Action |
 |---|---|
 | ↑ ↓ | move through the list |
-| Tab | switch between the list, steps and sessions |
+| Tab | switch between the list, steps, PRs and sessions |
 | `v` | next view: Timeline, Projects, Repos (`1` `2` `3` go straight to one; rumo remembers it) |
 | `h` | next horizon: Now, then Later, then Past, then Now again |
 | `s` | change status (1-5 picks directly) |
@@ -93,7 +97,11 @@ To get new plugin versions on their own, turn on auto-update for the `rumo` mark
 | `t` | toggle tags |
 | `n` | capture a new idea |
 | `e` | open the item in `$EDITOR` |
-| space | check or uncheck the selected step |
+| `a` | add a step to the selected item, after its open steps (below the highlighted one when the steps have focus); in the dialog, Tab switches `[agent]` and `[manual]` |
+| Enter, shift+↑ ↓, `d`, space | with the steps focused: edit, move, delete (asks first) or check the highlighted step; Esc goes back |
+| `x` | hide or show the done steps of every item (rumo remembers it) |
+| `p` | add a PR link to the selected item (a title may follow the link); in the dialog, Tab switches the state |
+| Enter, space, `e`, `d` | with the PRs focused: open the highlighted PR in the browser, change its state, edit it, or delete it (asks first) |
 | `c` | copy the command that resumes the selected agent session |
 | `/` | filter by title, tag, group or text (Esc clears) |
 | `q` | quit |
@@ -108,13 +116,22 @@ To get new plugin versions on their own, turn on auto-update for the `rumo` mark
 | `/rumo now` | List what is in progress, with the next step of each. |
 | `/rumo find <text>` | Search past, current and future items. |
 | `/rumo status` | Show where you left off on the linked item. |
-| `/rumo step <text>` | Add a step to the linked item. |
+| `/rumo step <text>` | Add a step to the linked item, or to the item it belongs to when none is linked. |
 | `/rumo park [reason]` | Pause the item with an accurate "Left off" and stop updating it here. |
 | `/rumo done` | Finish the item (checks the steps, asks first). |
 | `/rumo unlink` | Stop updating the item from this session. |
+| `/rumo sessions [7d]` | Catch up on the sessions open or active since the last review: create or update their items. |
+
+`link`, `status`, `park`, `unlink` and `sessions` need Claude Code with the plugin, because they rely
+on its session id and hook. Other agents get the rest.
 
-`link`, `status`, `step`, `park` and `unlink` need Claude Code with the plugin, because they rely on
-its session id and hook. Other agents get the rest.
+`/rumo sessions` is for when you worked in several sessions without rumo. From any session, it reads
+what each recent Claude Code session did (where it ran, what you asked, what it edited, the PRs it
+opened) and matches it to an item: the one it is linked to, one that worked on the same branch, or one
+about the same subject, before proposing a new item. Quick questions are proposed as ignored. You see
+one short plan (update, link, create, ignore) and nothing is written until you say yes or adjust it.
+Each review starts where the last one ended (3 days back the first time); `/rumo sessions 7d` looks
+further back. Sessions run by scripts (`claude -p`) and in temporary folders are left out.
 
 When you create an item or an idea, the agent checks whether it belongs to an existing group. If
 other ungrouped items look like the same initiative, it suggests a new group (name and color) and
@@ -128,9 +145,24 @@ follow several topics: when you start something no linked item covers, the agent
 track it as a new item, add it as a step, or leave it out. Left off is one line and Context at most
 three. `/clear` starts a new, unlinked session; `claude --resume <id>` picks the old one up again.
 
-In a session without an item, once it edits files, the agent asks whether to track it. The first time
-it also asks whether to keep asking in future sessions (`ask_to_track` in the config). If you say no,
-it reminds you that the option exists every 15 days or 15 sessions.
+You can add, edit, move, check and delete steps in the Timeline too. On your next message, a linked
+session is told which steps changed since its last answer, so it neither redoes nor re-adds them, and
+it starts none of them unless you ask. When the agent finishes a step and more remain, it ends with
+the next one: an offer to start it, or a note that it is yours.
+
+Each item lists its pull requests (GitHub, GitLab, Bitbucket or any other link) with their state:
+open, draft, merged or closed. rumo finds them on its own: a PR a linked session opens (with
+`gh pr create`, `glab mr create` or a tool that creates PRs) goes into its item at the end of the turn,
+and while the Timeline is open, the GitHub CLI (`gh`, when installed and logged in) keeps their states
+current and adds the PRs opened from the branches the item's sessions worked on. The agent updates a
+state when it learns one, and you can add, edit, open and delete PRs in the Timeline too; a PR you
+delete is never added back. The list shows how many PRs of each item are still open.
+
+In a session without an item, the agent learns at the start what is in progress in that repository
+(up to three items, with their next step), so it can answer "what is left?"; `rumo now` lists
+everything in progress. Once that session edits files, the agent asks whether to track it. The first
+time it also asks whether to keep asking in future sessions (`ask_to_track` in the config). If you
+say no, it reminds you that the option exists every 15 days or 15 sessions.
 
 ## Item format
 
@@ -155,12 +187,17 @@ Users land on a protected page after logging out.
 - [ ] [manual] Ask for a PR review
 - [ ] [agent] e2e test for logout
 
+## PRs
+- [open] https://github.com/you/web-app/pull/42 Redirect home after logout
+
 ## Sessions
 - 2026-10-11 10:08 | web-app (main) | 7134aad0-4ba6-4583-9503-c08e98d28270 | /Users/you/repo/web-app
 ```
 
 - Statuses: `idea`, `doing`, `waiting`, `paused`, `done`. `done: <date>` is set when an item is finished.
 - Steps are `[agent]` (the AI can do it) or `[manual]` (you or someone else does it).
+- PRs are one link per line, with the state in brackets (`open`, `draft`, `merged`, `closed`; none when
+  unknown) and an optional title after the link.
 - An idea can be just the frontmatter; it grows when you start working on it.
 - A session line ending in `| closed` no longer updates the item.
 

{rumo_cli-0.3.0 → rumo_cli-0.5.0}/README.md

@@ -42,6 +42,10 @@ system language.
   /plugin install rumo@rumo
   ```
 
+  `/rumo` runs its `rumo` commands without asking. To let the agent run them without asking in later
+  answers too (to link an item it offered to create, for example), add `"Bash(rumo:*)"` to
+  `permissions.allow` in `~/.claude/settings.json`.
+
 - **Codex, Gemini CLI, Cursor, GitHub Copilot and other agents** that read `SKILL.md` files,
   simple mode (create items and ideas, list and search them; no automatic updates):
 
@@ -64,7 +68,7 @@ To get new plugin versions on their own, turn on auto-update for the `rumo` mark
 | Key | Action |
 |---|---|
 | ↑ ↓ | move through the list |
-| Tab | switch between the list, steps and sessions |
+| Tab | switch between the list, steps, PRs and sessions |
 | `v` | next view: Timeline, Projects, Repos (`1` `2` `3` go straight to one; rumo remembers it) |
 | `h` | next horizon: Now, then Later, then Past, then Now again |
 | `s` | change status (1-5 picks directly) |
@@ -72,7 +76,11 @@ To get new plugin versions on their own, turn on auto-update for the `rumo` mark
 | `t` | toggle tags |
 | `n` | capture a new idea |
 | `e` | open the item in `$EDITOR` |
-| space | check or uncheck the selected step |
+| `a` | add a step to the selected item, after its open steps (below the highlighted one when the steps have focus); in the dialog, Tab switches `[agent]` and `[manual]` |
+| Enter, shift+↑ ↓, `d`, space | with the steps focused: edit, move, delete (asks first) or check the highlighted step; Esc goes back |
+| `x` | hide or show the done steps of every item (rumo remembers it) |
+| `p` | add a PR link to the selected item (a title may follow the link); in the dialog, Tab switches the state |
+| Enter, space, `e`, `d` | with the PRs focused: open the highlighted PR in the browser, change its state, edit it, or delete it (asks first) |
 | `c` | copy the command that resumes the selected agent session |
 | `/` | filter by title, tag, group or text (Esc clears) |
 | `q` | quit |
@@ -87,13 +95,22 @@ To get new plugin versions on their own, turn on auto-update for the `rumo` mark
 | `/rumo now` | List what is in progress, with the next step of each. |
 | `/rumo find <text>` | Search past, current and future items. |
 | `/rumo status` | Show where you left off on the linked item. |
-| `/rumo step <text>` | Add a step to the linked item. |
+| `/rumo step <text>` | Add a step to the linked item, or to the item it belongs to when none is linked. |
 | `/rumo park [reason]` | Pause the item with an accurate "Left off" and stop updating it here. |
 | `/rumo done` | Finish the item (checks the steps, asks first). |
 | `/rumo unlink` | Stop updating the item from this session. |
+| `/rumo sessions [7d]` | Catch up on the sessions open or active since the last review: create or update their items. |
+
+`link`, `status`, `park`, `unlink` and `sessions` need Claude Code with the plugin, because they rely
+on its session id and hook. Other agents get the rest.
 
-`link`, `status`, `step`, `park` and `unlink` need Claude Code with the plugin, because they rely on
-its session id and hook. Other agents get the rest.
+`/rumo sessions` is for when you worked in several sessions without rumo. From any session, it reads
+what each recent Claude Code session did (where it ran, what you asked, what it edited, the PRs it
+opened) and matches it to an item: the one it is linked to, one that worked on the same branch, or one
+about the same subject, before proposing a new item. Quick questions are proposed as ignored. You see
+one short plan (update, link, create, ignore) and nothing is written until you say yes or adjust it.
+Each review starts where the last one ended (3 days back the first time); `/rumo sessions 7d` looks
+further back. Sessions run by scripts (`claude -p`) and in temporary folders are left out.
 
 When you create an item or an idea, the agent checks whether it belongs to an existing group. If
 other ungrouped items look like the same initiative, it suggests a new group (name and color) and
@@ -107,9 +124,24 @@ follow several topics: when you start something no linked item covers, the agent
 track it as a new item, add it as a step, or leave it out. Left off is one line and Context at most
 three. `/clear` starts a new, unlinked session; `claude --resume <id>` picks the old one up again.
 
-In a session without an item, once it edits files, the agent asks whether to track it. The first time
-it also asks whether to keep asking in future sessions (`ask_to_track` in the config). If you say no,
-it reminds you that the option exists every 15 days or 15 sessions.
+You can add, edit, move, check and delete steps in the Timeline too. On your next message, a linked
+session is told which steps changed since its last answer, so it neither redoes nor re-adds them, and
+it starts none of them unless you ask. When the agent finishes a step and more remain, it ends with
+the next one: an offer to start it, or a note that it is yours.
+
+Each item lists its pull requests (GitHub, GitLab, Bitbucket or any other link) with their state:
+open, draft, merged or closed. rumo finds them on its own: a PR a linked session opens (with
+`gh pr create`, `glab mr create` or a tool that creates PRs) goes into its item at the end of the turn,
+and while the Timeline is open, the GitHub CLI (`gh`, when installed and logged in) keeps their states
+current and adds the PRs opened from the branches the item's sessions worked on. The agent updates a
+state when it learns one, and you can add, edit, open and delete PRs in the Timeline too; a PR you
+delete is never added back. The list shows how many PRs of each item are still open.
+
+In a session without an item, the agent learns at the start what is in progress in that repository
+(up to three items, with their next step), so it can answer "what is left?"; `rumo now` lists
+everything in progress. Once that session edits files, the agent asks whether to track it. The first
+time it also asks whether to keep asking in future sessions (`ask_to_track` in the config). If you
+say no, it reminds you that the option exists every 15 days or 15 sessions.
 
 ## Item format
 
@@ -134,12 +166,17 @@ Users land on a protected page after logging out.
 - [ ] [manual] Ask for a PR review
 - [ ] [agent] e2e test for logout
 
+## PRs
+- [open] https://github.com/you/web-app/pull/42 Redirect home after logout
+
 ## Sessions
 - 2026-10-11 10:08 | web-app (main) | 7134aad0-4ba6-4583-9503-c08e98d28270 | /Users/you/repo/web-app
 ```
 
 - Statuses: `idea`, `doing`, `waiting`, `paused`, `done`. `done: <date>` is set when an item is finished.
 - Steps are `[agent]` (the AI can do it) or `[manual]` (you or someone else does it).
+- PRs are one link per line, with the state in brackets (`open`, `draft`, `merged`, `closed`; none when
+  unknown) and an optional title after the link.
 - An idea can be just the frontmatter; it grows when you start working on it.
 - A session line ending in `| closed` no longer updates the item.
 

{rumo_cli-0.3.0 → rumo_cli-0.5.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "rumo-cli"
-version = "0.3.0"
+version = "0.5.0"
 description = "Your dev work, past, now and later: Markdown files, a terminal Timeline, and AI agents that keep it current"
 readme = "README.md"
 requires-python = ">=3.11"