@trybullet/cli 1.4.9 → 1.4.11

package/README.md

@@ -28,6 +28,23 @@ everything live. Connect a cloud provider or explicitly download the optional on
 - **Tools:** read / write / edit / delete, `search_code`, `find_files`,
   `run_command`, background processes, web search + fetch, and a real browser
   (below). File tools reach any absolute path; commands run from the workspace.
+- **Remote SSH workspaces.** Open `user@host:/path/to/project` — from the
+  sidebar (**Connect over SSH…**) or `bullet -C user@host:/path` — and Bullet
+  works on that machine. Transport is your own `ssh` binary, so `~/.ssh/config`,
+  IdentityFile, ssh-agent, ProxyJump and `Host` aliases (Daytona, Tailscale,
+  etc.) all just work; one multiplexed ControlMaster connection carries every
+  command. The remote folder is mirrored locally (dependency trees excluded),
+  file tools edit the mirror — diffs, snapshots and rewind included — while
+  every `run_command`/`start_process` executes on the host: edits rsync across
+  before each command, and whatever the command changed (lockfiles, generated
+  code, git commits) syncs back after it. When a remote dev server prints a
+  localhost URL, its port is forwarded over the same connection so Preview and
+  the agent's browser reach it. Hosts without rsync fall back to tar-over-ssh.
+  Keys, ssh-agent, password and key-passphrase prompts, first-use host
+  confirmation, and keyboard-interactive/MFA are supported; secrets go directly
+  to OpenSSH and are never saved. A one-off key file (a cloud provider's `-i`
+  key) can be set in the SSH input or with `--ssh-key <file>`; it is remembered
+  per host. Use `ssh://user@host:2222/path` for non-standard ports.
 - **Code search that lands.** `search_code` is extended-regex, so `(a|b)`, `\d`
   and `+` mean what the model thinks they mean — grep's default dialect treats
   them as literal characters, which silently answered "no matches" for code that
@@ -99,7 +116,9 @@ the provider auth are byte-for-byte the same code the app runs.
 npm link                          # puts `bullet` on your PATH
 bullet account signup             # create a Bullet account (first run also offers this)
 bullet account guest              # start without an email; upgrade later without losing history
-bullet auth                       # Claude / ChatGPT subscription, or an API key
+bullet providers                  # connect or inspect providers and local servers
+bullet auth openrouter            # connect a specific provider directly
+bullet auth status                # show every connection
 bullet                            # interactive session in this folder
 bullet "fix the failing tests"    # run one task, then keep talking
 bullet -p "what does app.js do"   # print and exit — pipeable
@@ -108,7 +127,47 @@ git diff | bullet -p "review this"
 
 Inside a session: `enter` sends, `ctrl+j` newlines, `esc` stops a running turn,
 `tab` completes `/commands` and `@files`, `↑` walks history. `/help` lists the
-rest — `/model`, `/cost`, `/diff`, `/undo`, `/resume`, `/agents`.
+rest — `/providers`, `/model`, `/thinking`, `/cost`, `/diff`, `/undo`, `/resume`, `/agents`.
+`/login` signs in to your Bullet account; `/providers` connects and switches model providers.
+
+### Providers and thinking
+
+`bullet providers` (or `bullet auth`) presents the full provider surface: Claude and ChatGPT/Codex
+subscriptions; Anthropic, OpenAI, xAI, Gemini (Google AI Studio), Groq, and
+OpenRouter API keys; Ollama and LM Studio local servers; and a custom
+OpenAI-compatible endpoint. Each connection keeps its own encrypted key,
+endpoint, and selected model, so adding one never replaces another.
+
+Provider presets are used when you press Enter at the base-URL prompt:
+
+```bash
+bullet auth gemini       # Google AI Studio
+bullet auth groq
+bullet auth openrouter
+bullet auth ollama       # http://localhost:11434/v1
+bullet auth lmstudio     # http://localhost:1234/v1
+bullet auth custom       # enter an HTTPS endpoint
+bullet auth status
+```
+
+Endpoints without a scheme are saved as HTTPS. HTTP is accepted only for
+loopback local servers. Local servers do not require a key. Use a provider and
+thinking level per run or per session:
+
+```bash
+bullet --provider openrouter --model openai/gpt-5.2 --thinking high "review this"
+bullet --provider ollama --model qwen3-coder "fix the tests"
+# in a session — unconfigured providers connect before becoming active
+/providers gemini
+/model gemini-2.5-pro
+/thinking high            # auto | low | medium | high | xhigh | max
+```
+
+`--effort` remains an alias for `--thinking`. The setting is persisted in the
+session and forwarded only where the selected model supports it: OpenAI
+reasoning models, Claude, supported xAI/Gemini/Groq models, and OpenRouter
+models that advertise reasoning metadata. Unsupported local and compatible
+models receive no reasoning parameter, so the setting does not cause API errors.
 
 Skills come across from Claude Code and Codex without the desktop app:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@trybullet/cli",
-  "version": "1.4.9",
+  "version": "1.4.11",
   "description": "The fastest coding agent — terminal edition. Same router, tools and agent loop as the Bullet desktop app, in your shell.",
   "license": "UNLICENSED",
   "homepage": "https://codewithbullet.com",
@@ -24,11 +24,11 @@
     "bin/bullet.js"
   ],
   "optionalDependencies": {
-    "@trybullet/cli-darwin-arm64": "1.4.9",
-    "@trybullet/cli-darwin-x64": "1.4.9",
-    "@trybullet/cli-linux-x64": "1.4.9",
-    "@trybullet/cli-linux-arm64": "1.4.9",
-    "@trybullet/cli-win32-x64": "1.4.9"
+    "@trybullet/cli-darwin-arm64": "1.4.11",
+    "@trybullet/cli-darwin-x64": "1.4.11",
+    "@trybullet/cli-linux-x64": "1.4.11",
+    "@trybullet/cli-linux-arm64": "1.4.11",
+    "@trybullet/cli-win32-x64": "1.4.11"
   },
   "engines": {
     "node": ">=18"