Skip to content
Back to search

inbox

MarketplaceWorks with Claude CodeGitHub

A plugin for Claude and Codex that intelligently manages outstanding questions, tasks, issues, and opportunities into one nicely organized place alongside your session.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026. Its scripts were only partly scanned.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/petekp/inbox with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/petekp/inbox'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/petekp--inbox/badge.svg)](/listings/petekp--inbox)

HTML

<a href="/listings/petekp--inbox"><img src="/api/listings/petekp--inbox/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

If you're like me, just paste a link to this Github repo to your agent and ask it to install.

If you want to do things the old way, proceed...

Claude Code

In a Claude Code session in the terminal, type:

/plugin install inbox --marketplace petekp/inbox

Answer `y` to add the marketplace, then choose a scope. It starts working in that session. A user-scope install also covers Code sessions in the Claude desktop app on this machine.

To install from the Claude desktop app instead, open a Code session:

1. Click **+** beside the prompt, then **Add plugins**. 2. In the Directory, click **+** at the top right, then **Add from a repository**. 3. Enter `petekp/inbox` and click **Sync**. 4. Click **+** on Inbox.

This installs it for your user account, so it works in the terminal too. `/plugin` does not run in the desktop app, and the inbox does not reach the app's cloud sessions.

If your organization manages Claude Code, an inbox you install yourself works only in part. Claude Code skips the hooks it uses to add to what Claude reads, so Claude gets neither the inbox's instructions nor its list of what waits on you. The inbox also keeps the old conversation's list after `/clear` or a resume, and shows no permission prompts or failed turns. Questions, tasks and findings still reach it. To get everything, ask an admin to list the inbox in your organization's managed settings.

To update, run these, then `/reload-plugins` in any session that's already open:

claude plugin marketplace update inbox
claude plugin update inbox

- It makes one Sonnet call after each of Claude's replies. See [Cost](#cost). - It was built and tested with Claude Code 2.1.300.

Codex

codex plugin marketplace add petekp/inbox
codex plugin add inbox@inbox

Then, in the ChatGPT desktop app, trust the plugin's hooks: click the hook icon beside the prompt's approval setting, then Allow all. Codex runs a plugin's hooks only after you trust them. To open the inbox, press + at the top right of the window, then choose More tools, then Inbox.

[codex/README.md](codex/README.md) covers updating and running the `codex` command from inside the app.

For both

The PRs tab needs the GitHub CLI, `gh`, signed in.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 5 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. {
  2. "name": "inbox",
  3. "owner": { "name": "Pete Petrash" },
  4. "plugins": [{ "name": "inbox", "source": "./" }]
  5. }
README.md · README · 430 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # Inbox
  2. I have ADHD. Working with an agent in a chat thread format is very cognitively taxing. The number of things you're having to hold in your head begins to compound the longer the session goes on. The questions, bugs, ideas, and tasks all begin to pile up and intermix making it difficult to keep everything in line.
  3. Inbox provides immediately apparent relief here by giving your agent an organized, stable place to surface everything that needs a decision. Inbox also makes sure your agent always provides a proactive, anticipatory set of quick actions on each item, including a recommended action.
  4. Even better, Inbox provides your agent a place to surface latent issues and opportunities, ones that it might otherwise gloss over in the interest of exclusively addressing the task at hand.
  5. Inbox is available for Claude Code in the terminal and desktop app, Codex in the ChatGPT desktop app, and omp in the terminal. Each variant is uniquely crafted for each platform, but works in same fundamental way in all of them.
  6. ## How it works
  7. https://github.com/user-attachments/assets/a493119c-4d8b-46e0-a18a-bd0ecf041b6b
  8. ## Install
  9. If you're like me, just paste a link to this Github repo to your agent and ask it to install.
  10. If you want to do things the old way, proceed...
  11. ### Claude Code
  12. In a Claude Code session in the terminal, type:
  13. ```
  14. /plugin install inbox --marketplace petekp/inbox
  15. ```
  16. Answer `y` to add the marketplace, then choose a scope. It starts working in
  17. that session. A user-scope install also covers Code sessions in the Claude
  18. desktop app on this machine.
  19. To install from the Claude desktop app instead, open a Code session:
  20. 1. Click **+** beside the prompt, then **Add plugins**.
  21. 2. In the Directory, click **+** at the top right, then **Add from a
  22. repository**.
  23. 3. Enter `petekp/inbox` and click **Sync**.
  24. 4. Click **+** on Inbox.
  25. This installs it for your user account, so it works in the terminal too.
  26. `/plugin` does not run in the desktop app, and the inbox does not reach the
  27. app's cloud sessions.
  28. If your organization manages Claude Code, an inbox you install yourself
  29. works with two differences. After `/clear` or a resume, it loads that
  30. conversation's list at your first message. A permission prompt reaches the
  31. inbox about a second and a half after it appears. To get everything, ask
  32. an admin to list the inbox in your organization's managed settings.
  33. To update, run these, then `/reload-plugins` in any session that's already
  34. open:
  35. ```sh
  36. claude plugin marketplace update inbox
  37. claude plugin update inbox
  38. ```
  39. - It makes two Sonnet calls after each of Claude's replies, one for the rows and one for the Status tab. See [Cost](#cost).
  40. - It was built and tested with Claude Code 2.1.300.
  41. ### Codex
  42. ```sh
  43. codex plugin marketplace add petekp/inbox
  44. codex plugin add inbox@inbox
  45. ```
  46. Then, in the ChatGPT desktop app, trust the plugin's hooks: click the hook icon
  47. beside the prompt's approval setting, then Allow all. If the icon isn't there,
  48. open Settings, then Hooks, then Inbox, then Trust all. Codex runs a plugin's
  49. hooks only after you trust them. On Codex 0.164.0 and later, an update stops
  50. the hooks, so trust them again after each update. To open the inbox, open the
  51. side panel and choose the ⋯ menu beside New, then Inbox. This was checked on
  52. 2026-11-14 in the ChatGPT app with Codex 0.169.
  53. [codex/README.md](codex/README.md) covers updating and running the `codex`
  54. command from inside the app.
  55. ### omp
  56. ```sh
  57. omp plugin marketplace add petekp/inbox
  58. omp plugin install inbox@inbox-omp
  59. ```
  60. The inbox starts working in the next omp session. `omp plugin list` shows it
  61. as `inbox@inbox-omp`. It reads `.omp-plugin/marketplace.json`, which omp looks
  62. for before the `.claude-plugin/` folder that Claude Code reads.
  63. To update, run these, then restart omp:
  64. ```sh
  65. omp plugin marketplace update inbox-omp
  66. omp plugin upgrade inbox@inbox-omp
  67. ```
  68. After each reply, the inbox makes two model calls, one to update the rows and one to write the Status tab. It uses
  69. the first of these that your omp can run:
  70. 1. The model your `@inbox` role names.
  71. 2. The newest Sonnet from your providers, `anthropic` first.
  72. 3. Your `@smol` role.
  73. To set `@inbox`, add it under `modelRoles` in omp's `config.yml`, then restart
  74. omp:
  75. ```yaml
  76. modelRoles:
  77. inbox: anthropic/claude-sonnet-5-5
  78. ```
  79. Only Sonnet is tested. Another model may work, but nobody has checked how well.
  80. Your provider bills each call at that model's rate.
  81. If `@inbox` is unset, or names a model omp cannot use, such as an unknown model
  82. or one you are not signed in to, the inbox uses the next choice. The panel's
  83. footer shows the model it uses. A model that omp can use but that fails when
  84. called does not fall through: that update fails, and the next reply retries it.
  85. Without a usable model, the footer says "no inbox model: set @inbox" and the
  86. inbox cannot update.
  87. ### For all
  88. The PRs tab needs the GitHub CLI, `gh`, signed in.
  89. ## Using it
  90. Type `/inbox` in Claude Code or omp, or open the Inbox tab in the ChatGPT app. The
  91. inbox has four tabs: Status, Asks, Finds and PRs.
  92. ### Status
  93. Where the session's work stands, for someone coming back to it cold. The page
  94. names what the session is focused on now, then each part of the work with
  95. where it stands. A part idle for a day says how long. Subagents and other work
  96. running under a part show beneath it. A part that waits on a question or task
  97. of yours says so, and View opens it. A line marks where you last looked, so
  98. what changed since then sits above it. Finished work folds into a count you can
  99. open.
  100. You can set a goal with a finish line, such as "2.5 in the store". The page
  101. then groups the work under the goal's milestones, and the inbox keeps the goal
  102. and its milestones current. You can edit or remove the goal at any time. One
  103. you typed stays until it is met. One the inbox inferred moves on when the work
  104. does.
  105. The page is a guide to the work, not a log. The second model call after each
  106. reply writes it. When that call fails, the page says so.
  107. ### Asks
  108. Questions the agent asked you, and tasks only you can do.
  109. The agent doesn't have to do anything special to put a question here. After
  110. each reply, a model reads what the agent wrote and records each question in
  111. it, with its possible answers. The agent's recommended answer comes first.
  112. Press an answer and it goes to the agent as your message, a few seconds later,
  113. so Undo can take back a wrong press. You can also type
  114. your own reply, or press Explain to have the agent say more before you decide.
  115. When a question is a design choice, such as two layouts or two ways to build a
  116. feature, Compare has the agent try each answer against your code and make a
  117. page that shows them side by side, which opens from the question. The page
  118. leads with the agent's pick, and the agent's reply gives the pick, its reason
  119. and the page's path. Where the agent can run a subagent in the background, the
  120. comparison runs there, so you can keep working. The question reads
  121. "Comparing…" until the agent reports back. After 30 minutes with no report, it
  122. reads "No comparison came back", and you can press Compare again.
  123. A task is something like signing in or adding an API key. It comes with
  124. buttons for its steps, such as copying a command or opening a file. In Claude
  125. Code, running the command with `!` closes the task once it succeeds. Dismiss
  126. drops a task you won't do, without a message to the agent.
  127. ### Finds
  128. Bugs, risks and ideas the agent noticed outside the task it's working on. The
  129. agent records them and carries on with its task, and you decide later which
  130. ones to act on. Fix on an issue, or Do it on an idea, hands it to the agent.
  131. File issue has the agent file it in your issue tracker, such as Linear or
  132. GitHub, or link the issue that already covers it. Reply sends your own words
  133. about it. Explain has the agent say why it matters and what fixing it would
  134. involve, without acting. Discuss talks it through, and Dismiss drops it.
  135. ### PRs
  136. Pull requests from this session and your current branch. Each one is marked
  137. Blocked, Ready or Waiting, and lists what blocks it: review comments waiting
  138. on you, failing checks and merge conflicts. Buttons hand the work to the
  139. agent: address one review comment or all of them, draft a reply, fix a
  140. failing check, resolve conflicts, or merge. Fix and Resolve conflicts show only
  141. while GitHub still shows the problem. A PR that merges or closes leaves the tab
  142. on its own, with Undo to keep it there. Clear merged and closed, at the top of
  143. the tab, clears any that stay, except your current branch's own.
  144. Your agent can also put the PRs in an order, such as which to merge first. The
  145. tab then lists them first, numbered, under what the order is for and why. When
  146. a ranked PR changes, the tab says so and offers Rank again.
  147. ### It keeps itself up to date
  148. When you answer a question in your own message, a task gets done, or the
  149. agent fixes a finding, the inbox closes the item. Closed items fold away under
  150. the open ones, each with how it ended. One you dismissed keeps Reopen there for
  151. the rest of the session.
  152. The agent reads the inbox too. Beside each of your prompts, it sees what's
  153. still open and what you answered, even after the conversation is compacted.
  154. Every press shows what it did right away. Discuss reads "Discussing…" until
  155. the agent replies, then "✓ Discussed".
  156. ### In each app
  157. Help lists the keys and what each mark means.
  158. - **Terminal:** each action shows the letter that runs it. The number keys
  159. switch tabs, and `j` and `k` move up and down. On the Status, they move
  160. between the rows that have a button, and the letter beside a button presses
  161. it. ctrl+x tab moves focus from the prompt to the line above it, then to the
  162. panel, then back to the prompt.
  163. - **Claude desktop app:** you click. Type `/inbox` to open the pane. Clicks in
  164. the pane are checked on the Claude Code engine 2.1.309 and later. On 2.1.295,
  165. a click after a press could only give the pane its focus back.
  166. - **ChatGPT app:** you click, or press the same keys as in the terminal. The
  167. tab shows no letters.
  168. - **Herdr app:** see [Herdr app pane](#herdr-app-pane).
  169. - **omp:** `/inbox` opens the panel over the conversation, and esc closes it.
  170. Each action shows the letter that runs it, and Reply is `t`. Arrow keys move
  171. between rows and between a row's buttons, and enter presses the focused
  172. button. Tab, or the number keys, switch tabs. On the Status, `j` and `k`
  173. move between the rows that have a button, and the up and down arrows scroll
  174. the page.
  175. In Claude Code, a line above your prompt counts what needs you and the
  176. findings waiting, with a button that opens the panel. When Claude stops on an
  177. error, a second line says why, with a Resume button after an API error. The
  178. ChatGPT app has no such line. omp has a line with the same counts. It says
  179. `/inbox` opens the panel, and it has no stop line.
  180. ### Herdr app pane
  181. In a Herdr app terminal, the inbox can open in a pane beside the terminal.
  182. 1. Start Claude Code, omp or Codex in a Herdr app terminal. The first time, the
  183. inbox asks "Install the inbox's Herdr mod?". Press Install.
  184. Claude Code and omp ask in their own inbox. Codex asks on the ChatGPT app's
  185. Inbox tab.
  186. 2. Type `/inbox` in Claude Code or omp. The inbox opens in a pane to the right
  187. of the terminal. Claude Code's Open inbox button does the same.
  188. 3. The pane shows the inbox of the terminal you last focused in its tab. It has
  189. Asks, Finds and PRs, and you can press every button. ← and → switch tabs,
  190. `j` and `k` move between rows, and esc gives the keys back to the terminal.
  191. Help lists the rest.
  192. Don't install saves your answer. Run `/inbox herdr` in Claude Code or omp to be
  193. asked again.
  194. The Codex CLI has no `/inbox`. Open the pane for it with
  195. `herdr-app do pane.split '{"direction":"right","pane":"<pane id>","mod":"inbox"}'`,
  196. taking the pane id from `herdr-app ls`.
  197. Inside a Herdr pane, Claude Code, omp and the Codex CLI also report to Herdr's
  198. sidebar, as pane tokens:
  199. | Token | Holds |
  200. |---|---|
  201. | `inbox` | What waits on you, in one line |
  202. | `inbox-needs-you`, `inbox-findings`, `inbox-prs` | The tab's count alone, such as `2`. `inbox-needs-you` is the Asks tab's, and `inbox-findings` the Finds tab's. Empty when the tab has nothing waiting. |
  203. | `inbox-stop` | Why the agent stopped. The count tokens stay empty until the stop clears, so the sidebar has room for it. |
  204. | `inbox-focus` | What the session is focused on, from its Status. A session that started this one as a Herdr delegate shows it as the delegate's row. No sidebar row needs it. |
  205. To tell the counts apart by each tab's color, add this row to `rows` under
  206. `[ui.sidebar.agents]` in Herdr's config:
  207. ```toml
  208. [
  209. { token = "$inbox-stop", fg = "#ffa3b0" },
  210. { token = "$inbox-needs-you", fg = "#ffae42" },
  211. { token = "$inbox-findings", fg = "#cab0ff" },
  212. { token = "$inbox-prs", fg = "#8cc8c0" },
  213. ],
  214. ```
  215. Herdr puts ` · ` between the tokens that have a value, and leaves the line out
  216. when none has one.
  217. To see every part with sample items in Claude Code, run `/inbox demo`. Presses
  218. on them change only the samples and send nothing. Press Hide demo, or run the
  219. command again, to go back to your own items. `/inbox demo recording` shows the
  220. same samples without the notices that mark them, for recording a video. Run
  221. `/inbox demo` to end it.
  222. ## Cost
  223. In Claude Code, the inbox adds two things:
  224. | What the inbox adds | Tokens | Cost at API prices |
  225. |---|---|---|
  226. | A Sonnet call after each of Claude's replies, to update the inbox | 3–4k in, about 2k of it cached. 100–250 out. | About 0.5¢ per reply, or 1¢ after 5 idle minutes |
  227. | A second Sonnet call, to write the Status tab | About 1.2k in and 14–44 out on a short exchange (three eval runs: 1,175–1,214 in). A catch-up over a conversation reads more: 1,358 in and 100 out in the one run. | Less than the first call, which reads about 3k in |
  228. | Its instructions and tools, sent with every request Claude makes | About 1,350, cached | Under 0.1¢ per request |
  229. On a Claude plan, these count toward your usage limits.
  230. In Codex, the update after each reply runs through the `codex` binary inside
  231. the desktop app, with your Codex sign-in. It makes two calls per reply. Each
  232. carries about 12,000 input tokens of base instructions, which every
  233. `codex exec` call includes, plus its own prompt. The earlier single call came
  234. to about 16,000. It counts toward your plan's usage.
  235. ## What it runs, sends and changes
  236. This covers the Claude Code mod. [codex/README.md](codex/README.md) covers
  237. the Codex plugin. The omp extension runs the same `gh` queries. Its update
  238. request goes through omp's own connection to the provider of the model it
  239. uses, and holds the same things as the Claude Code request.
  240. **What leaves your machine.** Three things, and nothing else:
  241. - After each of Claude's replies, the inbox sends two Sonnet requests to
  242. Anthropic through Claude Code's own model connection. Both hold your last
  243. prompt, Claude's reply, the inbox's open items, and a line for each tool
  244. Claude ran. A tool line reads like `ran: npm test` or
  245. `edited src/app.ts`. [Cost](#cost) gives the request's size.
  246. - When the inbox may have missed a turn, it asks the same model, with the same two calls, to update it
  247. from the whole conversation. It forks the conversation for this, or reads
  248. the transcript after a resume.
  249. - To fill the PRs tab, it runs read-only `gh` queries: `gh pr view`, and
  250. `gh api graphql` for review threads. They reach GitHub under your own `gh`
  251. sign-in. The inbox never reads your GitHub token.
  252. **Programs it starts.**
  253. | Program | When |
  254. |---|---|
  255. | `gh` | To fill the PRs tab |
  256. | `open` | When you press a button that opens a link, file or folder |
  257. | `test -x` | Before opening a file. An executable file is shown in Finder, not run. |
  258. | `herdr pane report-metadata` | Only inside a Herdr pane, to show what waits on you and each tab's count in Herdr's sidebar |
  259. **Messages it sends as you.** When you press an answer or action button, the
  260. inbox sends Claude a message in your name. The message is the answer you
  261. chose, or a request about the item, such as asking Claude to fix a finding.
  262. Resume, on a stopped turn, sends `Continue`. Every message it sends starts
  263. from a press. When you mark a task Done that Claude is waiting on, the inbox
  264. tells Claude a few seconds later, or once Claude's running turn ends.
  265. **What it adds to Claude's context.**
  266. - Its instructions, about 1,350 tokens, in every request.
  267. - A note beside your prompt when you answer one of Claude's numbered
  268. questions, or when the inbox changed since Claude last saw it.
  269. - Its open items after the conversation is compacted, so Claude keeps them.
  270. **What its hooks see.**
  271. - Tool calls. The inbox reads each call to write the tool lines above, to
  272. show a question while Claude's question dialog is open, and to find a PR
  273. this session opens with `gh pr create`. It passes every call on unchanged,
  274. except calls to its own two tools. `record` saves a question, a task or a
  275. finding and `close` closes an item. The inbox answers these itself, so they run
  276. without a permission prompt.
  277. - Permission prompts. While Claude Code asks you to approve a tool call, the
  278. inbox shows a row for it, then passes the request on unchanged. It never
  279. approves or denies a permission prompt.
  280. - Tool descriptions. It lists its own two tools to Claude up front, instead
  281. of behind tool search. It leaves other tools' descriptions alone.
  282. - Shell commands you run with `!`, and their output. A command that runs
  283. with nothing on stderr closes a task that asked you to run it.
  284. - Session starts. After `/clear`, a resume or a fork, the inbox loads that
  285. conversation's items. It passes the event on unchanged.
  286. - Your theme setting, to match its colors.
  287. **What it keeps.** The inbox saves each session's items, and the PRs it
  288. tracks, in Claude Code's plugin storage on this machine. It keeps the 40
  289. most recent sessions and deletes older ones. An item can summarize part of
  290. the conversation, so it may name the people in it. Nothing goes to the
  291. plugin's author.
  292. It also adds the `/inbox` command.
  293. ## Developing
  294. Read [AGENTS.md](AGENTS.md) first. [docs/looks.md](docs/looks.md) says which
  295. file owns each rule and where the four looks differ on purpose.
  296. Run the mod from a clone:
  297. ```sh
  298. claude --plugin-dir /path/to/inbox
  299. ```
  300. The session reloads the mod when you change one of its files.
  301. The Codex plugin shares the rules in `hooks/` with the mod. Rebuild its
  302. bundles after changing either:
  303. ```sh
  304. npm --prefix codex ci # once
  305. npm --prefix codex run build
  306. ```
  307. [codex/README.md](codex/README.md) covers trying a build in Codex.
  308. The omp extension in `omp/` shares the rules in `hooks/` too. It runs on Bun,
  309. and omp installs it from a bundle, so rebuild the bundle after changing
  310. `omp/src` or the shared modules:
  311. ```sh
  312. bun install --cwd omp --frozen-lockfile --ignore-scripts # once
  313. npm --prefix omp run build
  314. ```
  315. Bun's bundler writes different output in different Bun versions. So the build
  316. runs the Bun version that `omp/package.json` pins, whichever Bun starts it, and
  317. the install above puts that Bun in `omp/node_modules`. The pin covers macOS on
  318. Apple silicon only. On another platform, add the matching `@oven/bun-*` package
  319. at the same version to the `devDependencies` in `omp/package.json`, or build
  320. with that Bun version installed.
  321. Try a build in omp with a fresh `HOME`, so it cannot touch your own omp
  322. settings or inbox: `env HOME=/path/to/empty/folder omp -e omp/src/host.ts`.
  323. `./scripts/check.sh` runs Prettier, a file-size check, `claude plugin validate`, a type check and
  324. the tests, and checks the Codex bundles and the omp bundle are current. The type check needs the
  325. types Claude Code writes to `.claude-plugin/types/` the first time it loads
  326. the mod.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.