igorcosta · Oct 29, 2026 · Oct 15, 2026 · Oct 17, 2026 · Oct 17, 2026 · Oct 17, 2026
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
@@ -187,6 +187,14 @@ jobs:
           AUTOHAND_SKIP_COMPUTER_CONTROL_INSTALL: '1'
         run: sh src/testing/scenarios/fresh-alpha-install.sh ./binaries/autohand-test ci-alpha-smoke
 
+      - name: Verify Git Bash shell execution
+        if: runner.os == 'Windows'
+        shell: bash
+        timeout-minutes: 10
+        run: |
+          cygpath --version
+          bun run test:ci tests/windowsShell.integration.test.ts tests/ui/ink/TeamPanel.test.tsx
+
       - name: Verify binary (Unix)
         if: runner.os != 'Windows'
         run: |
@@ -209,3 +217,30 @@ jobs:
           if ($LASTEXITCODE -ne 0) {
             throw "Windows --help smoke test failed with exit code $LASTEXITCODE"
           }
+
+  windows-tuistory:
+    runs-on: windows-latest
+    timeout-minutes: 15
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          fetch-depth: 0
+
+      - uses: actions/setup-node@v7
+        with:
+          node-version: 24
+          package-manager-cache: false
+
+      - uses: oven-sh/setup-bun@v2
+        with:
+          bun-version-file: package.json
+
+      - name: Install dependencies
+        run: bun install --frozen-lockfile
+
+      - name: Build CLI for terminal tests
+        run: bun run build
+
+      - name: Verify native team recovery from Git Bash
+        shell: bash
+        run: bun run test:tuistory tests/tuistory/team-activity.tuistory.test.ts
diff --git a/.github/workflows/installer-release-compatibility.yml b/.github/workflows/installer-release-compatibility.yml
@@ -0,0 +1,27 @@
+name: Installer release compatibility
+on:
+  pull_request:
+    paths:
+      - install.sh
+      - install.ps1
+      - scripts/install-computer-use.mjs
+      - src/testing/scenarios/released-installer-smoke.py
+      - .github/workflows/installer-release-compatibility.yml
+  schedule:
+    - cron: '21 6 * * *'
+  workflow_dispatch:
+permissions:
+  contents: read
+jobs:
+  released-installer:
+    timeout-minutes: 12
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+        channel: [stable, alpha]
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@v7
+      - name: Install the independently published binary in a clean HOME
+        run: python3 src/testing/scenarios/released-installer-smoke.py --channel '${{ matrix.channel }}'
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -2,6 +2,16 @@
 
 ## Unreleased
 
+### Added
+
+- Translate supported Claude Code user and project permission rules during import, with a dry-run preview, and remove raw settings and environment data left by earlier imports.
+
+### Fixed
+
+- Keep npm installation successful when optional Computer control setup fails, matching the standalone installers.
+
+- Restore the interactive composer after session export dialogs so typing and a clean exit remain available.
+
 ### Changed
 
 - Persistent goals (`/goal`, `/goals` and `--goal`) are enabled by default for 0.9.9. Existing explicit settings are preserved; `/experiments disable slash_goal` turns them off.

diff --git a/README.md b/README.md
@@ -23,6 +23,8 @@ Interactive sessions assess repository readiness in the background while you wor
 
 The shell installer includes [Zit](https://getzit.org) v0.1.2 by default on supported macOS and Linux platforms, preserving an existing installation and verifying release checksums. Use `--no-zit` or `AUTOHAND_SKIP_ZIT_INSTALL=1` to opt out. The Windows installer supports `-NoZit` and the same environment variable; it preserves an existing Zit installation and reports that native Windows binaries are currently unavailable. `autohand --zit` requires Git 2.38 or newer. Installing Zit does not initialize repositories.
 
+On Windows, running `install.sh` from Git Bash, MSYS, or Cygwin delegates to the native PowerShell installer and preserves installation options. Autohand launched from Git Bash uses Bash for command tools; see [shell settings](docs/config-reference.md#shell-settings) to choose an executable explicitly.
+
 The npm package includes checksum-verified Zit binaries for macOS and Linux on ARM64 and x64. `npm install -g autohand-cli` and `bun install -g autohand-cli` download them with the package, including when lifecycle scripts are disabled. Autohand uses `ZIT_BIN`, an existing `zit` on `PATH`, or its packaged binary, in that order. Rust and a separate Zit installation are not required. Native Windows Zit binaries are currently unavailable.
 
 - **Terminal-Native Agent**: Understands your codebase and executes approved changes from the CLI
@@ -107,7 +109,8 @@ bun add -g .
 
 ### Requirements
 
-- Bun ≥1.0 (`curl -fsSL https://bun.sh/install | bash`)
+- Node.js 22 or later (to run Autohand)
+- Bun 1.0 or later, only to build from source (`curl -fsSL https://bun.sh/install | bash`)
 - Git (for version control features)
 - ripgrep (optional, for faster search)
 
@@ -600,6 +603,13 @@ Create `~/.autohand/config.json` or use `config.toml`, `config.yaml`, or `config
 | llama.cpp   | `llamacpp`    | Local inference                                      |
 | MLX         | `mlx`         | Apple Silicon optimized                              |
 | Z.ai        | `zai`         | High-performance inference                           |
+| Anthropic   | `anthropic`   | Claude models with your own API key                  |
+| Azure OpenAI | `azure`       | Azure deployments via API key, Entra ID or managed identity |
+| Vertex AI   | `vertexai`    | Google models on Vertex AI                           |
+| xAI         | `xai`         | Grok models via API key or OAuth                     |
+| Cerebras    | `cerebras`    | Hosted fast inference                                |
+| NVIDIA      | `nvidia`      | NVIDIA-hosted models                                 |
+| Sakana AI   | `sakana`      | Sakana AI models                                     |
 
 ## Session Management
 
@@ -803,7 +813,7 @@ We welcome contributions! Please read our [Contributing Guide](CONTRIBUTING.md)
 
 ### Common Issues
 
-**Installation fails**: Make sure you have Bun installed and up to date.
+**Installation fails**: Make sure Node.js 22 or later is installed. Building from source also needs Bun.
 
 **Permission denied**: Check your file permissions and try running with appropriate privileges.
 

diff --git a/docs/cloud-blog-draft.md b/docs/cloud-blog-draft.md
@@ -4,7 +4,7 @@ Editorial draft. Keep unpublished until CLI and Desktop release readiness and na
 
 Start a hosted agent from the terminal, close the terminal while it works, and reconnect to the saved conversation. Autohand Cloud adds `--cloud`, `/cloud`, `/handoff`, and `/open` to the CLI. The same session can be reviewed in Code Web and an updated Autohand Desktop app.
 
-Cloud CLI sessions are available only to Pro, Pro+, and Max accounts. Your selected account still needs active billing, model capacity, and permission to operate resources. A paid plan does not grant access to a repository that you have not authorized.
+Cloud CLI sessions need Pro, Pro+, Max, Team or Enterprise. Team and Enterprise need CLI 0.9.10 or later. Your selected account still needs active billing, model capacity, and permission to operate resources. A paid plan does not grant access to a repository that you have not authorized.
 
 ## Start a task where you work
 
@@ -83,7 +83,7 @@ Desktop links carry only a session ID and account ID. The remote cloud window ha
 
 The native CLI route authenticates a single account credential and forwards only allowlisted operations through the existing hosted API. It rechecks membership, ownership, write permissions, plan eligibility, model capacity, and repository grants. Browser cookies mixed with native bearer credentials are rejected. Responses remain private and are not cached.
 
-Only Pro, Pro+, and Max can admit new cloud work through this interface. Owned stop and queue cleanup remain available after a downgrade. If durable Jobs are unavailable, admission fails instead of falling back to execution tied to the terminal request.
+Only these plans can start new cloud work. Owned stop and queue cleanup remain available after a downgrade. If durable Jobs are unavailable, admission fails instead of falling back to execution tied to the terminal request.
 
 Local `--yes`, `--yolo`, custom MCP settings, system prompts, and tool-scope overrides cannot bypass hosted policy. Unsupported combinations fail before cloud launch. Local restrictions that Cloud cannot represent also fail closed. Read-only plan mode can preserve deny rules limited to mutating workspace operations; other custom restrictions require local execution.
 

diff --git a/docs/cloud.md b/docs/cloud.md
@@ -1,7 +1,7 @@
 # Autohand Cloud from your terminal
 
-Cloud CLI sessions are available only to **Pro, Pro+, and Max** accounts. Free,
-Lite, Team, and Enterprise accounts cannot start cloud work through this interface.
+Cloud CLI sessions need Pro, Pro+, Max, Team or Enterprise. Team and Enterprise need CLI 0.9.10 or later.
+Free and Lite accounts cannot start cloud work through this interface.
 The selected account also needs write access, active billing, available model
 capacity, and repository authorization. Sign in with `autohand login`.
 

diff --git a/docs/config-reference.md b/docs/config-reference.md
@@ -1683,7 +1683,7 @@ git add -A && git commit -m "feat: add user dashboard with charts"
 
 ## Shell Settings
 
-Control what shell commands started by Autohand can see. This covers the `run_command` tool, `!` terminal commands, and streaming or interactive shells. Hook commands and MCP server processes have their own launchers and are not affected.
+Choose the shell used by `run_command`, foreground and background `!` commands, and streaming shells, and control their environment. Hook commands and MCP server processes have their own launchers and are not affected.
 
 ```json
 {
@@ -1700,13 +1700,17 @@ Control what shell commands started by Autohand can see. This covers the `run_co
 
 | Field         | Type     | Default | Description                                                                                          |
 | ------------- | -------- | ------- | ---------------------------------------------------------------------------------------------------- |
+| `executable` | string | auto | Shell executable or full path, such as `C:\\Program Files\\Git\\bin\\bash.exe`, `pwsh.exe`, or `/bin/zsh` |
+| `dialect` | string | inferred | `posix`, `cmd`, or `powershell`; requires `executable`. Controls command invocation and the syntax described to the agent |
 | `env.inherit` | string   | `all`   | `all` passes the whole parent environment; `essential` keeps PATH, HOME, USER, SHELL, TMPDIR, locale and terminal variables (plus their Windows equivalents); `none` starts empty |
 | `env.include` | string[] | `[]`    | Variable names or globs to add back on top of the inherited set                                      |
 | `env.exclude` | string[] | `[]`    | Variable names or globs removed after inheritance and includes                                        |
 | `env.set`     | object   | `{}`    | Values pinned for every command; applied last                                                         |
 
 Variables Autohand needs to run its own tooling (`AUTOHAND_*`, `AUTOHAND_CLI`, `AUTOHAND_HOME`, `CODEX_HOME`) are always present. Explicit per-command overrides supplied by a tool call still win over the policy.
 
+By default, macOS/Linux use `SHELL` or `/bin/sh`. Native Windows uses `ComSpec` or `cmd.exe`. When launched from Git Bash (`MSYSTEM` is set), Autohand resolves its Bash executable with `cygpath.exe` and uses POSIX command syntax. If that conversion fails, configure the full Windows path to `bash.exe`. Bug reports identify the selected command shell and dialect separately from the parent shell.
+
 ## Network Settings
 
 ```json
@@ -2411,6 +2415,7 @@ Configure MCP (Model Context Protocol) servers to extend Autohand with external
 | `headers`      | `Record<string, string>`            | No             | `{}`               | Custom HTTP headers for http/sse transport (e.g. auth tokens) |
 | `env`          | `Record<string, string>`            | No             | `{}`               | Environment variables passed to the server                    |
 | `autoConnect`  | `boolean`                           | No             | `true`             | Whether to auto-connect on startup                            |
+| `localOnly`    | `boolean`                           | No             | `false`            | Keep the server on this device; do not publish it to the account control plane |
 
 > Servers connect asynchronously in the background during startup without blocking the prompt. Use `/mcp` to manage servers interactively, or `/mcp add` to browse the community registry or add custom servers.
 
@@ -2564,6 +2569,18 @@ Only compatible command hooks are translated. Unsupported source HTTP, prompt/ag
 
 See [hook import compatibility](./hooks.md#import-hooks-from-another-coding-agent) for source file locations, event mappings, timeout defaults, supported responses, and manual-porting limits.
 
+### Import MCP Servers from Claude Code
+
+```sh
+autohand import claude --categories mcp
+```
+
+The importer reads user servers from `~/.claude.json`, current-project servers from `projects[<workspace path>].mcpServers` in that file, and project servers from `<workspace>/.mcp.json`. Use `--path <workspace>` when importing for a workspace other than the current directory.
+
+Stdio servers keep their `command`, `args`, and `env`; HTTP and SSE servers keep their `url` and `headers`. User servers are added to the selected user config. Project servers are added to `<workspace>/.autohand/settings.local.json`. Imported servers are saved with `autoConnect: false`, so review them before enabling them. Existing servers with the same name are preserved and reported as skipped (`already exists`).
+
+Environment values and headers are copied as configured. The importer does not print server values, and imported servers stay on this device instead of being published to the account control plane.
+
 ---
 
 ## Chrome Extension Settings
@@ -2956,6 +2973,10 @@ These flags override config file settings:
 | `--patch`                     | Generate git patch without applying changes                                                    |
 | `--output <file>`             | Output file for patch (used with --patch)                                                      |
 
+When a `--worktree` session ends, Autohand removes its worktree only when there are no uncommitted or untracked files and no commits missing from the original branch. A branch created for that session is also removed; pre-existing branches are retained. Otherwise it prints `Kept worktree <path> (branch <b>) with changes` so you can recover your work. This cleanup applies to interactive, command, patch, RPC and ACP sessions; tmux and Zit behavior is unchanged.
+
+The agent's `exit_worktree` tool follows the same preservation rule and returns to the original workspace. `keep: true` always keeps the worktree. `discard_changes: true` explicitly requests removal with changes and follows the deletion approval policy; the restricted client profile denies it. `keep` takes precedence when both options are set. Cleanup stops safely if Git cannot verify the worktree or original branch.
+
 ### Zit Sessions
 
 `--zit` is the counterpart of `--worktree` for repositories shared by several agents through [Zit](https://github.com/autohandai/getzit). Instead of a git worktree and branch, the session runs in a disposable copy of the repository's current Zit state, and its edits are recorded as one Zit change when the session ends.
@@ -3471,6 +3492,6 @@ Fantail ignores this setting; local sessions do not advertise it.
 
 `search.provider` accepts `autohand`, `browser-profile`, `exa`, `brave`, `parallel`, `google`, and `duckduckgo`. An explicit `--search-engine` wins over the saved setting in interactive, patch, automatic, RPC, and ACP modes.
 
-When no provider is selected, a signed-in account with server-verified paid access uses Autohand Web Search. Lite, Pro, Pro Plus, Max, Team, and Enterprise include this service through `https://dev.autohand.ai/api/native/web-search`; Free users configure an existing provider during standard or quick setup, or with `/search`. Queries are limited to 1,024 characters, 10 results, and 30 requests per account per minute. Access uses the selected Autohand account and existing account credentials; customers do not need Cloudflare credentials. A failed hosted search reports its status and does not change providers.
+When no provider is selected, a signed-in account with server-verified access uses Autohand Web Search. Verified Free accounts include 10 web searches a day, shared with Code Web for the same account and reset at 00:00 UTC. `/search` shows the remaining allowance. At the cap, the tool returns the upgrade link and reset time, and the CLI prints that notice once per session. Lite, Pro, Pro Plus, Max, Team, and Enterprise retain their included search access. Queries are limited to 1,024 characters, 10 results, and 30 native requests per account per minute. Access uses the selected Autohand account and existing account credentials; customers do not need Cloudflare credentials. A failed hosted search reports its status and does not change providers.
 
-Browser Profile is the local default. Connect Chromium through `/browser` or provide an available Chrome/Brave profile. A missing, locked, or blocked profile produces a setup error instead of silently switching to Google. Exa, Brave, and Parallel require `search.exaApiKey`, `search.braveApiKey`, or `search.parallelApiKey`, respectively, or `EXA_API_KEY`, `BRAVE_SEARCH_API_KEY`, or `PARALLEL_API_KEY`. Onboarding never saves a keyed provider with a blank key. Google and DuckDuckGo can be selected explicitly; automated requests may receive CAPTCHA challenges.
+Browser Profile is the local default. Connect Chromium through `/browser` or provide an available Chrome/Brave profile. Before launching the profile, Autohand checks its `SingletonLock`, including Chromium's symlink lock. With Chrome open, search uses the connected Chrome bridge first, then eligible Autohand Web Search, then one line directing you to `/search`. A locked profile with no fallback is not offered to the model. A closed profile keeps the existing browser search path. Exa, Brave, and Parallel require `search.exaApiKey`, `search.braveApiKey`, or `search.parallelApiKey`, respectively, or `EXA_API_KEY`, `BRAVE_SEARCH_API_KEY`, or `PARALLEL_API_KEY`. Onboarding never saves a keyed provider with a blank key. Google and DuckDuckGo can be selected explicitly; automated requests may receive CAPTCHA challenges.
diff --git a/docs/features.md b/docs/features.md
@@ -39,7 +39,7 @@ Autohand is an autonomous LLM-powered coding agent designed to work directly in
 - [ ] Search history and command palette
 
 ## Session Management
-- [x] [Cloud sessions](cloud.md): hosted execution, reconnect, queue steering, approvals, and local/cloud handoff for Pro, Pro+, and Max
+- [x] [Cloud sessions](cloud.md): hosted execution, reconnect, queue steering, approvals, and local/cloud handoff. Needs Pro, Pro+, Max, Team or Enterprise (Team and Enterprise from CLI 0.9.10).
 - [x] Auto-save to `~/.autohand/sessions`
 - [x] Resume with `/resume` or `autohand resume <id>`
 - [x] History tracking (interactions, tool outputs, agent thoughts)