👀 Nosy

Nosy about your product. Never your data.

A product manager inside your coding agent. It goes through your backend, git history and roadmap first, then checks what your rivals shipped, and tells you what to build next: sized, placed on the roadmap, with a receipt for every claim.

Your agent reads today's code. Nosy keeps what a session can't: the record of what merged and why, demand counted from your issues, and last week's answers.

The plugin is free and MIT. Nosy Cloud (cloud.nosy.sh) is live and free for now: a shared record for your team. It never changes what the plugin does. See a sample report (made-up data).

Install

Claude Code (terminal or desktop app):

/plugin marketplace add nosy-hq/nosy
/plugin install nosy@nosy

Send the two commands one at a time. In the desktop app the second one opens the plugin page: click Install plugin. claude plugin list should show nosy@nosy enabled. Start a new session (or run /reload-plugins), open your repo and run /nosy:move-in. Every plugin command is namespaced with the plugin name, so it is /nosy:<command>; the top-level skill is /nosy:nosy.

Codex, Cursor, Gemini CLI, Copilot, OpenCode, Kiro don't know /plugin. In your project, run:

npx github:nosy-hq/nosy install

Or tell your agent: "Read https://github.com/nosy-hq/nosy/blob/main/llms.txt and install Nosy in this repo." Then type /nosy (Codex: $nosy). If your agent asks you to trust Nosy's hooks, there are four small ones, each with an off switch (docs/INSTALL.md).

Needs git and Node 18.17 or newer. Run move-in once (/nosy:move-in from the plugin, /nosy move-in from a skill install): it reads your README, docs, decision files, git history and, through gh if you have it, issues and PRs. move-in ends with /nosy:tour, which says first what Nosy reads, writes and sends, then asks its questions once instead of one per step. The counting runs on your machine with no model.

Try these first

Type	You get
/nosy:nosy	The 2–3 commands worth running in this repo, each with the reason. (Skill-only install: /nosy.)
/nosy:peek	What shipped, what didn't, what has no screen.
/nosy:canwe "can we do X?"	The code that already exists, the size from git history, and how often it was asked for.
/nosy:psst	What you could ship this week. Asked for + ready goes first.

Show your team

Optional. nosy publish turns the pm/ folder into a page your whole team can open: your next decision, where you stand against every rival, what customers ask for, the week on one page. Free for now. Your Cloud token goes in a file, never on a command line (docs/INSTALL.md).

Tested against a plain agent

psst ("what could we ship this week?") against the same agent without Nosy, same repo, same question, blind. Judged by models, run by us:

Run	Nosy–plain (gradings)
1	0–1: plain won
2	1–2: plain won
3	2–2: a tie
4	5–1: Nosy won, after we fixed what the losses showed

Precision in run 4: 16 of 16 items held for Nosy, 18 of 28 for plain. The fixes came after the losses, so these runs are not independent, and two of three questions are one private app. Method, limits and every loss: docs/EVALS.md.

Other agents

Nosy is one skill folder (skill/, the open Agent Skills format) plus small dependency-free Node scripts.

Where	How
Claude Code (default)	/plugin marketplace add nosy-hq/nosy then /plugin install nosy@nosy
Any coding agent, one command	In your project: npx github:nosy-hq/nosy install. It finds which of Claude Code, Codex, Cursor, Gemini CLI, Copilot, OpenCode and Kiro your project uses and copies the skill into each one's folder. nosy update and nosy uninstall touch only what it wrote. Then type /nosy (Codex: $nosy).
Windsurf, Roo, Junie…	Copy the skill folder: npx skills add nosy-hq/nosy, or by hand into the agent's skills folder. Then ask "Nosy, psst" or /nosy psst.
Any MCP client (Claude Desktop, Cursor, Zed, VS Code…)	npx github:nosy-hq/nosy mcp as a stdio server
GitHub Actions (weekly, no model key)	uses: nosy-hq/nosy@main, see docs/examples/nosy-weekly.yml
Slack / Discord	The Action, or nosy notify, posts the weekly "Psst…" to a webhook.
Terminal, no agent	npx github:nosy-hq/nosy weekly

npx github:… runs code straight from a repo. To know which code, pin a release tag: npx github:nosy-hq/nosy#v0.21.2 install. Every path in detail: docs/INSTALL.md.

Commands

Command	What it does
/nosy:nosy	Suggests the 2–3 commands worth running now. (Skill-only install: /nosy.)
/nosy:move-in	Learns your product, rules and roadmap. Run once.
/nosy:tour	The first look in one go: what Nosy reads and writes, then one list of questions.
/nosy:shipped	What reached your integration branch, and which decision each change was for.
/nosy:peek	What shipped, what didn’t, what has no screen.
/nosy:psst	What you could ship today. Asked for + ready goes first.
/nosy:canwe <question>	“Can we do X?” Answered with a size; remembered next week.
/nosy:atlas	Where next? Candidate markets researched on the same axes and checked twice; a matrix that ranks only what is verified. A suggestion, never an assignment.
/nosy:neighbors	What rivals shipped, and how much of it you already have.
/nosy:overheard [hours]	Which open PRs and issues serve which decision.
/nosy:spill <topic>	A spec your agents can build from. Stays local.
/nosy:scoop	The roadmap, in waves.
/nosy:roadmap	The roadmap in your repo: Now / Next / Later as a pull request on ROADMAP.md. Merging is the approval.
/nosy:handoff	Put one item of your list on GitHub where your team already works: an issue, a suggested assignee, a coding agent through a label, a project card. Shown first, written only with your yes.
/nosy:tea	One shareable decision page.
/nosy:map	What your product is made of: apps, screens, what’s off.
/nosy:dresscode	Your design system, checked in 20 areas, with a receipt for each.
/nosy:frontyard	Is your landing page behind the product, or ahead of it?
/nosy:stakeout

Most commands have a terminal twin that runs with no model, for example npx github:nosy-hq/nosy peek (see docs/CLI-CONTRACT.md for which, and for the ones that are agent only). npx github:nosy-hq/nosy rival-demand has no slash command: it lists what the users of your open-source rivals ask for most, from their public issues and Discussions. npx github:nosy-hq/nosy todo has no slash command either: it is the list of what only a person can do, or said they would (an account, a payment, a submission under your name). Your agent files an item instead of leaving it in a chat that ends, the first line of your next session says what still waits, and the page shows it as "Waiting on people". It is not a task tracker: no due dates, no estimates. The items are files under pm/todo/ in your repo, so a teammate's agent sees the same list.

1 skill · 21 commands · 106 scripts · 4 hooks · 16 named rules. Plain, dependency-free Node: the counting runs in your terminal, in CI or as an MCP server, with no model and no API key. Your agent adds the judgment. Everything Nosy remembers lives in a pm/ folder in your repo.

If it broke

• Install looks broken: npx github:nosy-hq/nosy doctor --check checks Node, git, gh, the skill files and hooks, and prints the fix next to each failing line. Local, no network, writes nothing.
• Still stuck: open your agent in this repo and say: "Read AGENTS.md and docs/INSTALL.md, install Nosy for me."
• Uninstall: /plugin uninstall nosy@nosy (other agents: npx github:nosy-hq/nosy uninstall). Your pm/ folder stays; it's yours.

What Nosy reads, what leaves your machine

• Reads. Nosy reads your code, git history, GitHub issues and PRs including their text (titles, bodies, comments and author logins, through your own gh), your decision and roadmap docs, and public web pages.
• Writes. Nosy writes to your pm/ folder, plus a few named files: temporary files, a first-run marker, the skill folders nosy install copies, a hand-built page of yours when you run nosy page-adopt (after a copy in pm/.backup/), a branch and pull request in your own repo when you run nosy roadmap --pr --yes, one fixed comment on each issue your merged PRs closed when you run nosy ship-notes --yes, an issue (or the changes to one you already have: an assignee, a label) and its project card in your own repo when you run nosy handoff --yes, a project board and its fields when you run nosy handoff --setup-board --yes, a status update on your GitHub project board when you run nosy board-status --yes, and files you name with a flag. The optional weekly GitHub Action commits and pushes pm/state/ and the decision page only if you set commit: "true".
• Sends. Nothing of yours leaves on its own. Nosy's network calls are reads: the public rival pages you listed (and, for rivals you configure, public counters through nosy rival-signals: GitHub, npm, Apple's app lookup and job-board APIs), and GitHub through your own gh, including a read-only lookup of the #N issues your agent's answer cites (NOSY_CITE_GH=0 turns that off), and, when you run nosy rival-demand, the public issues and Discussions of the open-source rivals you name. nosy notify and nosy publish send something only when you run them, and publish is off until you configure a target and confirm (counts and structure, never quotes). Both stop on a secret or personal data unless you pass --allow-sensitive. The model call is your agent's.
• No telemetry. No analytics, usage pings or crash reports. The one call you didn't start yourself is a once-a-day read of a public version file, so the plugin can say when a newer Nosy is out (nothing about you in it; NOSY_NO_UPDATE_CHECK=1 turns it off).

What the plugin's hooks do on their own. Installing the plugin adds four hooks. They run on your machine, read local files and git, and print a short note to your agent. None of them sends your code, history or documents anywhere, and each has an off switch in the plugin's settings.

Hook	Runs when	What it does	Network
psst-summary	A session starts	Prints one line from pm/state/lowhanging.json, if it exists, and one line when a newer Nosy is out	Once a day, one GET of the public file .claude-plugin/plugin.json in this repo, nothing sent about you. NOSY_NO_UPDATE_CHECK=1 turns it off
after-commit	A commit, merge, pull, cherry-pick or gh pr merge finishes	Says which matrix gap the change may close and the next command; keeps the last commit id in one small temp file	None
never-check	A git commit or gh pr create finishes	Compares what went in with the "never" rules in pm/sources.json; never blocks	None
cite-check	The agent finishes an answer or writes a Markdown file, in a repo with pm/sources.json	Checks every file:line, quote, commit and #N it cites	A read-only lookup of each cited #N through your gh, only if sources.json names a repo. NOSY_CITE_GH=0 turns it off

Everything else that touches the network is a command you run (the plugin itself is updated by you: /plugin marketplace update nosy, then /plugin update nosy@nosy, docs/INSTALL.md): watch, sweep and weekly (a plain GET of the rival pages you listed), notify (to the Slack or Discord webhook you pass; its message includes up to five merged and three close-to-merge PR titles, and --dry-run prints it first) and publish (to the Cloud address you configured). The table of every path is in docs/DATA.md.

The exact list, and what masking does not cover: docs/DATA.md.

When to skip it

Skip Nosy if…	Why
You want a code reviewer	No comments on style, bugs or code quality. Ever.
You want a competitor tracker	Rivals are one input, checked second. It isn't an alert service.
The project has no git history, or is brand new	Little to count. Shipped rates on fewer than 10 rows read "too few to say".
You only have claude.ai chat	No repo access there, so the scripts don't run (details).
You want it to decide or act for you	It suggests. It never edits your page, pushes, or opens issues unless you ask.

Status

Early version, open source (MIT). No stability promise yet. Questions and bugs: issues. Also: CHANGELOG, SECURITY, CONTRIBUTING.