Nissy
Nissy for developers
Free- Session history stays on your machine, encrypted.
- Sensitive data, like passwords and IP addresses, is caught before anything leaves.
- Incognito records nothing.
- You see what's shared from your sessions.
A second pair of eyes on your coding agents.
Nissy watches your agent sessions, speaks up when an agent goes off track, and keeps a record of every decision.
Works with Claude Code, Codex, Copilot and more
Where Nissy helps out.
Nissy reads along as the agent works. Pick a session to see what it flags, and what it leaves alone.
Worth a look
The agent skipped part of your ask.
You said "keep the interface async". cache.get() is synchronous.
src/cache/lru.ts:18
Nissy for organisations · decision ledgerOrganisations
Skipped the flaky webhook test
beyond planbilling-svcagent, on its ownRaised queue timeout to 5 min
on planinfradeveloper
No decisions yet.
By default: decisions and summaries. Content only if your organisation turns it on.
What Nissy gives you.
Catch mistakes early.
Nissy speaks up while the agent works, so a skipped ask or a broken rule doesn't wait for review.
Keep the reasons.
Every decision is recorded, so anyone can ask why the code is the way it is, even after the people behind it have moved on.
Stay in control.
Your sessions stay on your machine. Your organisation sees only what its settings allow, and you can see what's shared.
Ask your decision ledger why.
Nissy records every decision your agents make, and who made it. Teams ask the shared ledger, even after people move on.
Decision ledgershop-api, billing-svc
| Decision | Decided by |
|---|---|
| Tried to delete all of db/migrationsshop-api · 24 Sep | agent, on its ownstopped |
| Made cache.get() synchronousshop-api · 22 Sep | agent, on its ownbeyond plan |
| Put an LRU cache in front of getProduct()shop-api · 22 Sep | agent, as askedno |
| Skipped the flaky webhook testbilling-svc · 9 Sep | agent, on its ownbeyond plan |
| Retried charges with no capbilling-svc · 9 Sep | agent, on its ownbeyond plan |
| Capped charge retries at 5billing-svc · 9 Sep | developerno |
2 of 6 decisions cited
Ask the ledgershared sessions only
Client
Why are charge retries capped at five?
Plan review flagged an uncapped retry loop on 9 Sep 1.
The developer capped it at five the same afternoon 2.
- 1Retry failed charges9 Sep · ledger: Retried charges with no cap
- 2Cap charge retries at 59 Sep · ledger: Capped charge retries at 5
Learn from every session.
Reports show what keeps going wrong and how to fix it at the source: a line for your AGENTS.md, a skill, or a check that catches it every time.
- Your standup, already written, from yesterday's digest.
- See which habits are improving and which are slipping.
Report1d7d14d
Habits over the last 6 weeks
- States the goal before the first promptimproving
- Names the files in scopesteady
- Says what must not changeslipping
- Asks for a test run before doneimproving
Suggested fixes
- Add to AGENTS.md"Ask before changing a public interface."rule
- Make it a checkFail CI when package.json gains a dependency nobody approved.check
Organisations
Where problems pile up.
See which repositories keep raising concerns, and what kind, week by week.
Concerns by repositorylast 8 weeks
| Repository | 3 Augthis week | Total |
|---|---|---|
| billing-svcmostly testing | 11 | |
| shop-apimostly scope | 11 | |
| inframostly security | 4 | |
| web-appmostly scope | 2 |
billing-svc is rising: 7 in the last 4 weeks, mostly testing.
What Nissy does differently.
Most tools look at the work before it starts or after it's written. Nissy watches while it happens.
- Before the agent starts
Planning tools set the direction up front.
- While it runs
Nissy reads each turn as it happens and prompts you there and then, while you can still change course.
- After the code is written
Code review checks the pull request once the decisions have already been made.
Developers keep their sessions. Organisations choose what they see.
Nissy for organisations
Talk to us- Summaries and decisionsdefault Title, summary and milestones of each shared session, every decision and who made it.
- Usage Sessions, tokens, cost and tool calls by agent, project and person.
- Full contentopt-in Prompts, replies and tool output, once it's turned on in the agent and in your organisation.
Developers are free. See pricing
Questions
Which harnesses are supported?
Claude Code, Codex and GitHub Copilot today, and we add more all the time. Using something else? Tell us which one.
Which platforms?
The desktop app runs on Windows and macOS.
Organisations Nissy for organisations also accepts sessions from any harness that sends OpenTelemetry.
Does Nissy change what my agent does?
No. Nissy doesn't edit your code or steer the agent. It tells you what it found and quotes where, and the next move is yours.
What does my manager see?
Organisations What your organisation's settings allow. By default that's each shared session's title, summary, milestones and decisions. Organisations can turn on full content, and can record every time an admin reads it.
Does anything change when I join an organisation?
Organisations Nissy works the same on your machine. What changes is what's shared: your organisation's settings decide that, from summaries and decisions up to full content.
Does Nissy help with audits?
Organisations Yes. Every decision in a shared session is recorded with who made it: you, the agent following you, or the agent on its own. Decisions that went beyond the plan are flagged. Retention is yours to set, and every deletion is logged with who made it.
Can we host it ourselves?
Organisations Yes. We can run it for you in the region you need, or you can run it in your own environment. Talk to us.
Try it on your next session.
