@niroai/niro 0.3.3 → 0.3.4

package/README.md

@@ -23,8 +23,8 @@ 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 new
+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:
 

package/docs/working-on-branches.md

@@ -41,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.
 
@@ -72,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,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@niroai/niro",
-  "version": "0.3.3",
+  "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