See what your agent gets wrong without Niro.

100 tickets, the kind you hand it every day. Filter by pattern, then open one and watch Niro get it right instead of guessing.

No use cases match these filters.

Symbol Resolution Add automatic retries with backoff to our LLM calls so a transient 5xx doesn't fail the whole build. A guess that looks right is still a guess. AccuracyFuture impact
Symbol Resolution Write an audit log entry every time a project build is executed, with who triggered it. Reading the wrong method is debugging the wrong bug. AccuracyTime
Symbol Resolution Rate-limit the webhook endpoint per provider so one noisy integration can't starve the others. A URL isn't a location — until Niro makes it one. AccuracyTime
Symbol Resolution Make the git provider client timeout configurable per environment instead of hardcoded. “An implementation” isn't “the implementation.” AccuracyFuture impact
Symbol Resolution Let ops change the retry limit without a redeploy. Read it from config with a sane default. Finding the name isn't finding the impact. AccuracyTime
Symbol Resolution Reject a project with zero repos at creation time instead of letting it fail later in validation. Same name, different code, wrong edit. AccuracyTime
Symbol Resolution Replace our local copy of the graph builder with the shared one from the AST parser module. The import line can lie. The graph doesn't. AccuracyTime
Symbol Resolution Add unit tests for the repo change detector. Make its HTTP client injectable so we can mock it. A named guess is not a type. AccuracyTime
Symbol Resolution Return the number of nodes written from the batch write so the build progress bar is accurate. The wrong overload compiles, then quietly misbehaves. AccuracyFuture impact
Symbol Resolution Add an async version of the batch write and switch the sync service over to it. A confident hallucination is still a bug you pay for. AccuracyCost
Blast Radius Refactor the LLM request method to take a request object instead of five loose parameters. Grep sees text. Niro sees callers. Future impactTime
Blast Radius Make the repo path parameter on the indexing job optional. The caller you forgot is the bug you ship. Future impactTime
Blast Radius Rename `projectId` to `id` on the project response DTO. The wire doesn't care what your compiler thinks. AccuracyFuture impact
Blast Radius Add a new build status `CANCELLED` and remove the old `ABORTED` value. An enum is a contract in disguise. AccuracyFuture impact
Blast Radius Remove the old v1 projects endpoint. It's been replaced by v2. Deprecated is a label, not a fact. AccuracyFuture impact
Blast Radius Change `NIRO_API_URL` to mean the base URL without the `/api` suffix. Shared config is shared blast radius. Future impactTime
Blast Radius Add a `durationMs` field to the build-completed event and drop `finishedAt`. Fire the event, break the listeners. AccuracyFuture impact
Blast Radius Make `BaseController` validate the project id on every request. A base-class edit is a broadcast. Future impactTime
Blast Radius Drop the `legacyScore` column from the projects query. The query changed; the readers didn't get the memo. AccuracyFuture impact
Blast Radius Make `normalizePath` strip trailing slashes too. The smallest functions have the biggest blast radius. AccuracyFuture impact
Call Tracing Users can update their account details. Make sure the new path is validated before it hits the database. Security answers shouldn't start with “probably.” AccuracyFuture impact
Call Tracing Add a database write timeout on the project update flow. Half a call chain is a wrong answer. AccuracyTime
Call Tracing This log line is spamming production. Which requests trigger it? “How did we even get here?” — answered. AccuracyTime
Call Tracing Add a feature flag around the new ranking helper. Direct callers are the tip. Niro shows the iceberg. AccuracyTime
Call Tracing Clean up the resolver module. Remove anything that isn't reachable anymore. Unreachable code is dead code with a pulse. Future impactTime
Call Tracing Make sure the export job can never trigger a re-index. Connected or not is a fact, not a feeling. AccuracyTime
Call Tracing Add an auth check before any project delete. Preconditions live upstream. Niro finds them. AccuracyTime
Call Tracing Trace where a build request ends up after it's queued, so we can add tracing ids. Async isn't a dead end — for Niro. AccuracyTime
Call Tracing The dependency walker sometimes blows the stack. Add a depth limit. You can't reason about depth you can't see. AccuracyTime
Call Tracing When someone clicks Rebuild in the UI, add a confirmation and make the backend idempotent. A plausible trace and the real trace aren't the same trace. AccuracyTime
Cross-Service Give me a picture of how our three services talk to each other before I change the auth headers. The call you can't grep is the one that pages you. AccuracyTime
Cross-Service The metrics consumer for build events is double-counting. Fix it at the source. Someone fires this event. Niro knows who. AccuracyTime
Cross-Service Add a `visibility` field to the project model. Shared models share pain. AccuracyFuture impact
Cross-Service Rotate the auth service's client secret. Your dependency diagram is probably wrong. Niro's isn't. AccuracyTime
Cross-Service Add a request id that survives the whole 'create project' flow, for support tickets. A request doesn't stop at the boundary. Neither should the trace. AccuracyTime
Cross-Service Return 202 instead of 200 from the build start endpoint since it's async now. Your 200 is someone's contract. AccuracyFuture impact
Cross-Service Rename the internal `/internal/graph/stats` endpoint to `/internal/graph/summary`. “Internal” is a hope, not a fact. AccuracyFuture impact
Cross-Service Add a `schemaVersion` to documents in the `graphs` collection. Shared storage is invisible coupling. AccuracyFuture impact
Cross-Service Add an index on `projects.updatedAt` to speed up the dashboard. The coupling you can't see is the one that bites. AccuracyFuture impact
Cross-Service Update the architecture diagram to match reality. Ship the code, not the diagram. AccuracyFuture impact
Dead Code Clean up the repo admin controller. Remove the precompute endpoint if nothing uses it. “Probably dead” is how outages start. AccuracyFuture impact
Dead Code Delete `LegacyResolver.java`, we replaced it last quarter. “No references” from grep isn't “no references.” AccuracyFuture impact
Dead Code Trim `StringUtils`. It's grown to 20 helpers and half look unused. Dead code isn't free — it taxes every read. CostFuture impact
Dead Code Speed up the test suite. Remove tests that don't test anything real. A test with no subject tests nothing. AccuracyCost
Dead Code Audit our feature flags and remove the dead ones. Dead flags are landmines with cobwebs. CostFuture impact
Dead Code Delete everything marked @Deprecated. Deprecated and dead are not the same word. AccuracyFuture impact
Dead Code Remove unused imports and the modules they point at. Used-looking isn't used. AccuracyCost
Dead Code We cut over to the new indexer last month. Remove the old one. Half a migration is two live paths. AccuracyFuture impact
Dead Code Prune the API. Which documented endpoints does nobody call? An endpoint nobody calls is attack surface for free. CostFuture impact
Dead Code Simplify the environment config. Drop keys nothing reads. Config nobody reads is config that misleads. CostTime
Onboarding I'm new here. Explain what the LLM client does and where it's used before I touch it. Onboarding is just guessing until someone hands you the map. AccuracyTime
Onboarding Add a caching layer between the service layer and the repositories. Folders are a wish. The graph is the truth. AccuracyTime
Onboarding I have a day to get oriented. What should I read first? Importance is measurable. Niro measures it. AccuracyTime
Onboarding Summarise `IndexService.java` for me. It's huge. A file too big to read is a file too risky to change. AccuracyTime
Onboarding Which code handles personal data? We're doing a privacy review. You can't protect what you can't locate. AccuracyFuture impact
Onboarding Walk me through what happens when a build is triggered. Understanding is a small set of the right files. AccuracyTime
Onboarding I need to change how resolution works. Where does resolution start? Every subsystem has a front door. Niro finds it. AccuracyTime
Onboarding Split the graph module into its own service. Coupling you can't see, you can't manage. Future impactTime
Onboarding List every external system this service depends on, for the ops runbook. Your third-party surface is bigger than you think. AccuracyTime
Onboarding Why do most changes end up touching `ProjectService`? The class everything touches is the class nobody dares change. Future impactTime
Refactoring Add retry with exponential backoff around the outbound HTTP calls. Refactors break on the callers you didn't check. AccuracyFuture impact
Refactoring Break up `IndexService`. It's too big. Cut a class along how it's used, not how it looks. Future impactTime
Refactoring Move `normalizeFqn` into the shared commons module. Move once, fix every caller once. AccuracyTime
Refactoring `safeExecute` just calls `execute`. Inline it. Some wrappers are load-bearing. AccuracyFuture impact
Refactoring Make the `projectId` parameter required on `resolve`. Your non-null rule meets someone's null. AccuracyFuture impact
Refactoring Tighten encapsulation on `GraphWriter`. Make its fields private. “Private” has to be earned by the callers. Future impactTime
Refactoring Change `BaseJob.run` to acquire a lock before running. Template methods broadcast to their overrides. AccuracyFuture impact
Refactoring Make `GraphWriter.write` asynchronous. Async changes when things happen — and who breaks. AccuracyFuture impact
Refactoring We have `ProjectRef` and `ProjectHandle`. Merge them. Two names, one idea, endless confusion. CostFuture impact
Refactoring Put `projectId` first in `resolve(name, projectId, options)`. Parameter order is a contract with every caller. Future impactTime
Root Cause The LLM-backed resolver flakes intermittently in production. Find out why. Fixing where it crashed isn't fixing why. AccuracyTime
Root Cause Builds started failing yesterday with a null project id. What changed? The culprit isn't always the last commit. AccuracyTime
Root Cause `graph.rootNode` is sometimes null when the writer runs. Find every way that happens. A null has a history. Niro reads it. AccuracyTime
Root Cause We're getting a crash on an empty repo list in the indexer. Who sends that? The crash is here. The cause is upstream. AccuracyTime
Root Cause The resolver works from the API but fails from the MCP tool. Why? Reproduce faster when you know the way in. AccuracyTime
Root Cause `GraphWriter.write` throws 'session not started' from one code path. Find it. Fix the caller, not just the symptom. AccuracyFuture impact
Root Cause Dashboard shows negative build durations. Where does that come from? The service that crashes rarely caused it. AccuracyTime
Root Cause Exports broke after the last release. Nothing in the export code changed. A text diff hides a structural break. AccuracyTime
Root Cause Failed builds show as successful. Some exception is being swallowed. A swallowed error is a bug with the lights off. AccuracyTime
Root Cause When a build fails halfway, what else has already happened that we need to undo? The error is loud. The side effects are quiet. AccuracyFuture impact
Code Review Find issues in this commit. It changes the account update handler, two files. Small diffs on hot paths aren't small. AccuracyFuture impact
Code Review Find issues in this commit. It adds a parameter to ProjectService.create. A green diff can still break the repo next door. AccuracyFuture impact
Code Review Check this commit for problems. It's a small change to normalizeFqn. Isolated in the diff, central in the graph. AccuracyFuture impact
Code Review Find issues in this commit. It adds GET /api/projects/{id}/summary. Two endpoints, one job, double the upkeep. CostFuture impact
Code Review Find issues in this commit. It replaces the old indexer with the new one. “Just in case” is how two code paths rot. CostFuture impact
Code Review Find issues in this commit. It tweaks the build-completed payload. New coupling should never be invisible. AccuracyFuture impact
Code Review Find issues in this commit. It fixes the resolver bug and the tests pass. Green tests that skip the change prove nothing. AccuracyFuture impact
Code Review Find issues in this commit. The message says it doesn't touch auth or masking. Security changes shouldn't hide in a diff. AccuracyFuture impact
Code Review Who should look at this commit to the graph writer? The right reviewer owns the ripple, not just the file. Future impactTime
Code Review Find issues in this commit. It refactors the project DTO, no behaviour change per the message. A refactor that changes a contract isn't a refactor. AccuracyFuture impact
Agent Accuracy Give me the full list of HTTP endpoints across our services for the API docs. Plausible and correct are different graphs. AccuracyTime
Agent Accuracy Where is `RetryPolicy` used? I want to change its defaults. A partial usage list is a half-finished edit. AccuracyFuture impact
Agent Accuracy Use the shared logger in the new service class. An invented import is a build waiting to fail. AccuracyCost
Agent Accuracy Add a `description` field to the project entity. Don't let the agent flip a coin on your code. AccuracyFuture impact
Agent Accuracy Is it safe to change the return type of `GraphWriter.write`? “Safe” without the blast radius is a guess. AccuracyFuture impact
Agent Accuracy Remove `ProjectService.findByAlias`, it's obsolete. Let the agent delete on proof, not on hope. AccuracyFuture impact
Agent Accuracy Explain how authentication works in this service. Your auth isn't the textbook. Niro reads yours. AccuracyTime
Agent Accuracy Write a helper that retries a call with exponential backoff. Every duplicate is a second thing to fix forever. CostFuture impact
Agent Accuracy Fix the off-by-one in the pagination. A fix in one copy is a bug in the other two. AccuracyFuture impact
Agent Accuracy Which services would be affected if the auth service goes down? The answer was one hop away the whole time. CostTime