Nissy Contact us

Keep the reasons, not just the code.

Nissy for organisations builds a decision ledger from your team's AI sessions. When someone asks why it's built this way, the answer is there, even after the people who made the call have moved on.

Contact us See pricing
Chat · billing-svcshared sessions only
Why do we cap charge retries at five?

Plan review flagged an uncapped retry loop on 9 Sep 1.

You capped it at five that afternoon, as the ledger shows 2 3.

Sessions

  • 1Retry failed chargesyou · 9 Sep
  • 2Cap charge retries at 5you · 9 Sep

Decision ledger

3Capped charge retries at 5you9 Sep

The ledger outlasts the team.

Luke left in June. His decisions are still here, with the sessions behind them, so whoever picks up billing-svc can still ask why.

Decision ledger · billing-svcMar to Sep
  1. Moved failed charges onto a queueQueue failed charges
    Luke left in June
  2. Kept charge amounts in centsQueue failed charges
    agent, following Luke
  3. Swallowed a webhook errorWebhook handler cleanup
    agent, on its own beyond plan
  4. Retried charges with no capRetry failed charges
    agent, on its own beyond plan
  5. Capped charge retries at 5Cap charge retries at 5
    you
  6. Stored retry count on the chargeCap charge retries at 5
    agent, following you
6 decisions · 2 went beyond the plan

Where problems pile up.

See which areas keep raising concerns, and what kind.

Concerns by repositorylast 8 weeks
Repository3 Augthis weekTotal
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's included.

  • Ask your repository

    Answers cite the sessions and decisions behind them.

  • Decision ledger

    Every decision, who made it, and which went beyond the plan.

  • Concerns by area

    By repository and category, week by week.

  • Controls

    What admins and members see, what gets stored, and project rules for what Nissy looks out for.

Built for audits.

For regulated teams, the record of what was decided and by whom, kept as your policy requires.

  • Every decision 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.

See as much as your policy needs.

  1. Summaries and decisions

    default

    Title, summary and milestones of each shared session, every decision and who made it.

    Sharing is off until the developer and your organisation both turn it on.

  2. Usage

    Sessions, tokens, cost and tool calls by agent, project and person.

    Counts only. No prompts or replies.

  3. Full content

    opt-in

    Prompts, replies and tool output, once it's turned on in the agent and in your organisation.

Developers join through an invitation in the desktop app, and from then on your organisation's settings apply to their sessions.

Visibility settingsCleverbit
  • Project members see each other's sessions
  • Administrators see session content
  • Record administrator content reads
RetentionClear content after 30 days, Delete rows after 180 days
Change log
  1. Maria turned on "Record administrator content reads"3d

Every switch can only narrow what your deployment allows, and every change is logged.

Works with your harnesses.

Sessions come in from the tools your developers already use.

  • Claude Code
  • Codex
  • GitHub Copilot
  • Any harness that sends OpenTelemetry

Where it runs.

Hosted by us.

We run and update it. We can host in the region your organisation needs.

Self-hosted.

Run Nissy for organisations in your own environment, so its data stays inside your boundary. We help you set it up.

Talk to us about hosting

Tell us about your team.

We'll come back with a setup and a quote.

Contact us Developer? Download free.
Nissy, a cyan spirit holding a glowing orb