@niroai/niro 0.3.2 → 0.3.4

package/README.md

@@ -14,17 +14,19 @@ One package gives you three things:
 
 ## Working on branches
 
-Niro indexes your team's code from one branch (usually main). When you work on a feature
-branch, Niro notices and refuses to answer from the old code. Your assistant will offer the fix:
+Your projects cover the repos and branches you chose to index. On every question, Niro routes
+to the project matching your repo and current branch. When you are on a branch **no project
+covers** (with real changes), Niro refuses to answer from stale code. Your assistant offers the fix:
 
 ```bash
 niro new-temp-project     # run once in the repo folder
 ```
 
 This creates your own private copy of the project that follows your branch and your
-uncommitted edits, live (keep `niro watch` running). Teammates are not affected and cannot
-see your copy. Switching branches needs nothing: Niro answers from your copy on the feature
-branch and from the shared project on main. When your branch is merged:
+uncommitted edits, live (keep `niro watch` running). Your original project is not changed.
+Switching branches needs nothing: Niro answers from your copy on the new
+branch, and from the matching indexed project on branches you already cover. When your branch
+is merged:
 
 ```bash
 niro discard-temp-project

package/docs/working-on-branches.md

@@ -1,8 +1,13 @@
 # Working on branches with Niro
 
-Niro indexes your team's code from one branch, usually main.
-When you work on your own branch, your code is different from what Niro indexed.
-This page explains what happens then. Two minutes to read.
+Your team decides what Niro indexes: you create projects, and each project
+covers the repos and branches you choose. One project might index main,
+another might index a develop or release branch. That is up to you.
+
+When you ask a question, Niro picks the project that matches your repo and
+the branch you are currently on. This page is about the moment when NO
+project matches: you created a new branch and changed code that no project
+has indexed yet. Two minutes to read.
 
 ## The short version
 
@@ -14,11 +19,12 @@ Run it in your repo folder when Niro asks for it. That is all.
 
 ## What you will see
 
-You create a branch and start changing code.
+You create a branch that no project covers and start changing code.
 Then you ask your AI assistant something about the code.
 
-Niro notices your branch is not the one it indexed. Instead of giving you
-a wrong answer based on the old code, it replies with something like:
+Niro notices that no project has indexed this branch. Instead of giving
+you a wrong answer based on some other branch, it replies with something
+like:
 
     I cannot answer this safely. Your branch has diverged
     from the branch Niro indexed.
@@ -35,8 +41,8 @@ It creates your own private copy of the project inside Niro.
 
 - The copy follows your branch, including changes you have not committed.
 - Every save updates the copy, as long as "niro watch" is running.
-- Teammates are not affected. They keep using the shared project.
-- Nobody can see your copy. Not even teammates on your account.
+- Your original project is not changed. It keeps its own index.
+- The copy is fully separate and disposable.
 
 From then on, answers come from YOUR code.
 
@@ -44,8 +50,9 @@ From then on, answers come from YOUR code.
 
 Nothing to do. Niro checks which branch you are on for every question.
 
-- On your feature branch: answers come from your private copy.
-- Back on main: answers come from the shared project.
+- On your new branch: answers come from your private copy.
+- On a branch one of your projects already indexes: answers come
+  from that project.
 
 ## When your work is merged
 
@@ -65,8 +72,9 @@ of your changes together.
 
 ## Common questions
 
-Can teammates see my unfinished code?
-No. Your copy is private to you.
+Does this change my original project?
+No. The original project and its index stay exactly as they were.
+The copy is separate; deleting it later loses nothing.
 
 Does this work with my AI assistant and my git host?
 Yes. Any assistant that supports MCP (Claude Code, Cursor, Windsurf,
@@ -78,8 +86,13 @@ No. Niro copies the existing index instead of re-reading your code.
 It normally takes seconds.
 
 I just created a branch and have not changed anything. Will Niro nag me?
-No. Your code is still identical to what Niro indexed, so Niro answers
-normally. It only steps in once your code actually differs.
+No. Your code is still identical to the branch you started from, so Niro
+answers normally. It only steps in once your code actually differs.
+
+We already have projects for main and develop. Do I need this?
+Not while you are on main or develop: Niro routes to the matching project
+by itself. You only need a temporary project for a branch that none of
+your projects cover.
 
 What if I really want an answer from the shared project while on my branch?
 Tell your assistant so. The answer will be clearly labeled as describing

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@niroai/niro",
-  "version": "0.3.2",
+  "version": "0.3.4",
   "description": "Niro — one package: the niro CLI plus the Niro MCP server (code intelligence for AI coding assistants).",
   "keywords": [
     "niro",

package/src/commands/init.js

@@ -171,7 +171,7 @@ async function init(pathArg, opts = {}) {
       }
     } else if (otherBranchOnly.length) {
       // Known repo, but you're on a branch Niro hasn't indexed → the honest answer is "sandbox it",
-      // not "already indexed". A sandbox indexes your branch privately (teammates unaffected).
+      // not "already indexed". A sandbox indexes your branch in a separate copy (original untouched).
       const where = otherBranchOnly
         .map((p) => `"${p.alias || p.project_id}"${p.indexed_branch ? ` (indexed on ${color.cyan(p.indexed_branch)})` : ""}`)
         .join(", ");
@@ -179,7 +179,7 @@ async function init(pathArg, opts = {}) {
       console.log(`\n${color.green("✓")} This repo is part of: ${where}.`);
       console.log(`  But ${yourBranch} isn't indexed by Niro — answers would reflect the indexed branch, not your local work.`);
       console.log(`  ${color.cyan("Run `niro sandbox` here")} to index your branch privately ` +
-        color.dim("(teammates unaffected; `niro discard` to undo)."));
+        color.dim("(original project unchanged; `niro discard` to undo)."));
       if (!opts.addTo) {
         if (prompt.isNonInteractive()) {
           console.log(color.dim(

package/src/commands/takeover.js

@@ -72,7 +72,7 @@ async function takeover(pathArg, opts = {}) {
   }
 
   console.log(`\n  Creating a temporary private project of ${color.bold(source.alias || source.project_id)}...`);
-  console.log(color.dim("  Your teammates' view of the project is not affected."));
+  console.log(color.dim("  Your original project is not changed."));
 
   // 2. Create-or-extend server-side (ADR-016). If you already have a temporary project of this project,
   // the backend EXTENDS it — adds this repo to the same copy — instead of minting a second one, so

package/src/index.js

@@ -157,7 +157,7 @@ function main() {
   program
     .command("new-temp-project [path]")
     .aliases(["sandbox", "takeover"])
-    .description("Create a temporary private project for this folder that reflects your branch + local edits, so Niro's answers match your work (teammates unaffected). Remove it with `niro discard-temp-project`.")
+    .description("Create a temporary private project for this folder that reflects your branch + local edits, so Niro's answers match your work (your original project is unchanged). Remove it with `niro discard-temp-project`.")
     .option("--project <id_or_alias>", "which project to base the temporary project on when the repo maps to several")
     .action((pathArg, opts) => run(async () => {
       const cmd = require("./commands/takeover");

package/src/mcp/setup.js

@@ -840,7 +840,7 @@ lost"). When the target of the question is a repo other than the current one:
 
 Niro indexes a repo at ONE branch (the team's tracked branch). Identity is (git url, branch): a graph
 built on \`main\` does NOT reflect your feature branch or uncommitted edits. A **temporary project** is a private,
-temporary index of your branch (\`niro new-temp-project\` to create, \`niro discard-temp-project\` to remove — teammates unaffected).
+temporary index of your branch (\`niro new-temp-project\` to create, \`niro discard-temp-project\` to remove — the original project is unchanged).
 
 - **Obey \`🔔 Niro ACTION\` notices.** When a tool result appends "the coding assistant should run
   \`niro new-temp-project\` / \`niro discard-temp-project\`", run that command with the Bash tool (cwd = that