needle-cloud 2.7.0 → 2.9.0-next.1790858060.tiny-fern.d6d8a59

package/CHANGELOG.md

@@ -4,6 +4,26 @@ All notable changes to this package will be documented in this file.
 The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
 and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
 
+## [2.9.0] - 2026-10-01
+### Added
+- Approved local project commands for creating Needle projects, installing packages, building, and deploying from Cloud chat.
+- Local CLI settings to disable AI file edits or project commands independently, even after Cloud approval.
+- CLI-created web projects in the local project registry, with `local_project_list` and `local_project_select` for choosing the project used by file tools.
+
+### Changed
+- Long-running AI project commands return job status and support cancellation.
+- AI project commands can target another explicit local project after fresh approval; approved dev commands start its server and open the reported local URL in the default browser.
+- AI project creation accepts an existing parent folder separately from the new project's name, including parent paths with spaces.
+- Renamed PC-facing MCP tools to `local_files_*` and `local_project_*`, and account lookup to `needle_my_account`.
+
+## [2.8.0] - 2026-09-30
+### Added
+- Project-scoped MCP tools for AI file creation, replacement, deletion, rename, Undo, Redo, and opening files in their default app.
+- Local checkpoints and user approval for AI file changes, plus project-check freshness tracking.
+
+### Changed
+- Local file discovery explains shallow listings and how to search subdirectories.
+
 ## [2.7.0] - 2026-09-29
 ### Added
 - `files_check_project` AI tool for checking the connected local web project's TypeScript errors, with compact diagnostics, filtering, and cached error details.

package/README.md

@@ -54,11 +54,13 @@ the current month's upload usage. Deleted content can be restored from Trash for
 
 [Needle Cloud AI](https://cloud.needle.tools/team#ai) can use local tools provided by this CLI to read project files, search your code, and inspect logs. You can enable or disable local tools in an individual chat. See the [Needle Cloud AI documentation](https://engine.needle.tools/docs/cloud/#needle-cloud-ai) for how this works with your Unity or Blender project.
 
-The `files_check_project` tool checks the connected web project's TypeScript configuration using its locally installed TypeScript compiler. It returns structured errors with file names and line numbers, without emitting build files or applying fixes. It does not run package scripts or install dependencies. Checks stop after 10 seconds and retain up to 100 diagnostics; an unavailable or interrupted check is never reported as passing. This checks current TypeScript errors, not lint rules, Unity/Blender code, or whether an error existed before an AI edit. Referenced projects are not built.
+Tools that access files on your machine use `local_files_*`; commands that create, install, build, start a dev server, or deploy a local project use `local_project_*`. Cloud chat asks for approval before running project commands or changing files. After creating a project, the CLI adds it to the local project list and selects it for file tools. The AI can use `local_project_list` and `local_project_select` to return to any registered web project; selecting one does not approve edits. An explicit path to another project for a command requires fresh approval. A running dev server opens its local URL in your default browser and can be stopped with `local_project_cancel`.
 
-By default, `files_check_project({})` runs a new check and returns five errors with short messages. Use `{ "mode": "results", "file": "Player.ts", "code": "TS2322" }` to filter the latest results without recompiling; both filters are optional. Pass the returned `nextOffset` as `offset` for another page. Use `{ "mode": "error", "index": 0 }` for more detail about an error, or omit `index` for the last matching error. Summary messages are capped at 300 characters and details at 2,000 characters, with truncation indicated. Cached results include their check time and remain available until another check replaces them, the selected project changes, or the CLI exits. Run a new check after editing files.
+The `local_files_check_project` tool checks the connected web project's TypeScript configuration using its locally installed TypeScript compiler. It returns structured errors with file names and line numbers, without emitting build files or applying fixes. It does not run package scripts or install dependencies. Checks stop after 10 seconds and retain up to 100 diagnostics; an unavailable or interrupted check is never reported as passing. This checks current TypeScript errors, not lint rules, Unity/Blender code, or whether an error existed before an AI edit. Referenced projects are not built.
 
-Use local tools only with trusted projects and dependencies: the installed TypeScript compiler runs on your machine. This is not an execution sandbox. The existing local-tool controls also govern `files_check_project`.
+By default, `local_files_check_project({})` runs a new check and returns five errors with short messages. Use `{ "mode": "results", "file": "Player.ts", "code": "TS2322" }` to filter the latest results without recompiling; both filters are optional. Pass the returned `nextOffset` as `offset` for another page. Use `{ "mode": "error", "index": 0 }` for more detail about an error, or omit `index` for the last matching error. Summary messages are capped at 300 characters and details at 2,000 characters, with truncation indicated. Cached results include their check time and remain available until another check replaces them, the selected project changes, or the CLI exits. Run a new check after editing files.
+
+Use local tools only with trusted projects and dependencies: the installed TypeScript compiler runs on your machine. This is not an execution sandbox. The existing local-tool controls also govern `local_files_check_project`.
 
 To block Needle Cloud AI from calling tools on this machine across all chats, run:
 
@@ -80,6 +82,15 @@ npx needle-cloud settings
 
 The setting is saved in `~/.needle/settings.json` for your user account on this machine and persists across restarts. A running local server applies changes automatically; no restart is required. Disabling remote AI tools keeps the local MCP server and Unity/Blender connections available. Enabling local tools in a chat does not override this CLI setting.
 
+You can separately turn off AI file changes or project commands on this machine:
+
+```bash
+npx needle-cloud settings local-file-edits false
+npx needle-cloud settings local-project-commands false
+```
+
+Both settings are enabled by default, but Needle Cloud chat still asks for approval before it edits a file or starts a project command. A Cloud approval cannot override a disabled local setting. Pass `true` to either command to turn that capability back on. Project commands cover creating a Needle project, installing packages, running its build or dev script, and deploying an existing build. These commands can run project or package scripts; a deployment publishes files to the selected team. `needle-cloud settings` shows the current values.
+
 See the [Needle MCP documentation](https://engine.needle.tools/docs/ai/needle-mcp-server) for available tools and how to connect other AI assistants.
 
 ## CI/CD