rumo

Your work, past, now and later. rumo is a local, file-based organizer for a developer's own work. Every piece of work is a Markdown file on your machine. Run rumo to see it all as a Timeline, and let your AI agent sessions keep it up to date while you work.

• Now: what you are doing or waiting on, with the next step of each item.
• Past: what you finished in the last two weeks (answers "what did I do?" for a standup).
• Later: ideas and paused work, so nothing you meant to do gets lost.

Items can belong to a group (an initiative): the title takes the group color and the footer shows a legend. The interface is in English; the content (titles, notes, steps) is in your own language.

Nothing leaves your machine. There is no server, no database and no sync with Jira or ClickUp (ask your agent to update those if you want).

Install

1. The rumo command (pick one):

uv tool install rumo-cli            # macOS, Linux, Windows (https://docs.astral.sh/uv/)
pipx install rumo-cli               # macOS, Linux, Windows
brew install pedrobuzzi/tap/rumo    # macOS, Linux

Then run rumo. The first run creates ~/rumo/ for your items and a config file with your system language.

2. Your AI agent (optional, but this is where rumo shines):

• Claude Code, full experience (the agent keeps linked items up to date):

  /plugin marketplace add pedrobuzzi/rumo
  /plugin install rumo@rumo
  

• 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):

  npx skills add pedrobuzzi/rumo
  

Update: uv tool upgrade rumo-cli (or pipx upgrade rumo-cli, brew upgrade rumo), and /plugin marketplace update rumo in Claude Code.

Uninstall: /plugin uninstall rumo@rumo, then uv tool uninstall rumo-cli (or pipx uninstall rumo-cli, brew uninstall rumo). Your items in ~/rumo/ are never touched.

Use

In the terminal: rumo opens the Timeline.

In an agent session: type /rumo for a menu that fits the moment, or go straight to:

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.

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 applies it only if you agree.

While a session is linked, the agent updates the item after every response in which something changed. /clear starts a new, unlinked session; claude --resume <id> picks the old one up again.

Item format

---
title: Redirect after logout
status: doing
group: auth
tags: [bug, frontend]
created: 2026-10-11 10:08
updated: 2026-10-11 16:30
---

## Left off
Point the redirect to the home page; the e2e test is still missing.

## Context
Users land on a protected page after logging out.

## Steps
- [x] [agent] Fix the logout handler
- [ ] [manual] Ask for a PR review
- [ ] [agent] e2e test for 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).
• 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.

Config

config.toml lives in ~/.config/rumo/ on macOS and Linux (or $XDG_CONFIG_HOME/rumo/) and in %APPDATA%\rumo\ on Windows. rumo index prints its path.

folder = "~/rumo"
language = "pt-BR"     # language of the content the agent writes; defaults to your system language
tags = ["bug", "feature", "refactor", "research", "spike", "review",
        "infra", "deploy", "meeting", "docs", "support", "tech-debt"]

[groups.auth]
name = "Auth migration"
color = "blue"         # blue, green, yellow, orange, red, magenta, purple, cyan

RUMO_DIR and RUMO_CONFIG override the folder and the config path.

Contributing

See CONTRIBUTING.md for the layout, tests, trying the plugin locally and how releases work.

License

MIT