@lardexx/arenacode 2.9.0 → 2.11.0

package/README.md

@@ -170,8 +170,15 @@ screenshots are `XGetImage` + `XGetPixel` encoded to PNG by the client itself (z
 and the X events the server delivered are compared with the requested keycodes, chords, buttons and pixels. On Wayland
 the XWayland display is used. `ui app launch` still starts the program's own `.desktop` command; nothing else is spawned.
 
-**macOS**: grant Accessibility to your terminal, and `brew install cliclick` for the mouse. On macOS/Linux the
-accessibility tree is not read: `ui state` returns windows and geometry as elements.
+**macOS** is native too, again with no helper binaries: mouse with `CGEventCreateMouseEvent` + `CGEventPost`
+(left/right/middle, double and triple click through the click-state field, drag interpolated), keyboard with
+`CGEventCreateKeyboardEvent` plus modifier *flags* (`cmd`, `ctrl`, `alt`, `shift`) and Apple's fixed `kVK_*`
+keycodes, typing through `CGEventKeyboardSetUnicodeString` so any character or emoji goes in without a layout,
+windows from `CGWindowListCopyWindowInfo` (number, bounds, owner pid), screenshots from `CGDisplayCreateImage`
+converted from BGRA to PNG by the client. `brew install cliclick` is gone. Only what CoreGraphics cannot do —
+launch an app, bring a window to the front, resize it — still uses `osascript`, which ships with macOS. Grant the
+terminal **Accessibility** (input) and **Screen Recording** (pixels) in System Settings → Privacy & Security.
+On macOS/Linux the accessibility tree is not read: `ui state` returns windows and geometry as elements.
 
 **Ask and Proceed / Proceed.** The desktop's Settings switch, `ctrl+x a` here (also `/ask`, `/proceed`,
 `--proceed`, and `arenacode config set approval proceed`). The default, **Ask and Proceed**, asks before commands,
@@ -254,7 +261,7 @@ The agent never touches your PC directly: it asks, and this client shows a card.
 
 | Card | Source | Executed here |
 |---|---|---|
-| **terminal** | `POST /task/<id>/local-exec` | PowerShell / `cmd` / WSL on Windows, `/bin/sh` elsewhere — asked before running unless `--yes` |
+| **terminal** | `POST /task/<id>/local-exec` | your shell — zsh/bash/sh/fish on macOS and Linux, PowerShell/pwsh/cmd/WSL/Git Bash on Windows (see [Shells](#shells)) — asked before running unless `--yes` |
 | **files** | `local-fs` | `ls`, `stat`, `read`, `write`, `replace`, `find`, `mkdir`, `mv`, `rm`, `pull`, `git_status`, `git_log`, `git_diff`, `git_commit`, `git_revert`, `git_publish` |
 | **plan** | `local-ui` `plan` | approve / reject / ask for a revision, right in the terminal |
 | **file from the agent** | `local_file` | downloaded from `GET /file?raw=1` into the open folder |
@@ -264,17 +271,65 @@ Every file path is resolved **inside the open folder**; paths that escape it are
 the folder itself. Local operations run with your user's permissions — `--confirm-writes` adds a confirmation for
 mutating file operations, `--yes` skips confirmations for terminal commands.
 
-### Not available in a terminal
+### Project context
 
-The desktop client can drive the whole PC (mouse, keyboard, screenshots, app launching — `local-ui`
-`control` / `type` / `keystroke` / `screenshot` / `app` / `state` / `apps` / `multi_*`). A terminal cannot, so
-those cards are answered with an explicit error instead of silently doing nothing:
+Every folder gets its own log, `context_<project>.md`, next to the files you are working on. It is the desktop
+client's file, with the desktop's own template (mined from `ArenaCode-x64.exe`):
 
-```json
-{ "ok": false, "error": "operation \"screenshot\" is not available in the terminal client: the ArenaCode desktop client is required" }
+```markdown
+# Contesto del progetto progetto-web
+
+Sessione: 2026-11-02 21:45 (nome-del-bridge.tunnl.gg)
+_Nessun task ancora._
+<!-- agente:inizio -->
+<!-- agente:fine -->
+
+Aggiornato automaticamente da ArenaCode a fine di ogni job. La API key non è scritta qui.
+```
+
+The title, the session label, the placeholder and the footer follow the interface language (`it`, `en`, `es`).
+What happens when:
+
+* **The folder opens or a session starts** → the client creates the file if it is missing, and adds a `Sessione:`
+  line for the new session. An existing file is **never overwritten**: the agent's block lives inside it.
+* **At the end of every task** the agent rewrites the block between `<!-- agente:inizio -->` and
+  `<!-- agente:fine -->` (date, task id, files changed, commits, decisions, what is still open, how it was checked —
+  at most 40 lines). The client saves it **at once, without Accept or Reject**: the card only shows what changed.
+* **The first task of a new bridge session** carries the whole file as `project_context`, so the bridge writes it
+  to `runtime/project_context.txt` and tells the agent to read it in parts (`agentctl.py context --part N`). Later
+  tasks do not repeat it — a new bridge (`/health` → `started_at`) or a different folder makes it travel again.
+  The file is never summarised or truncated.
+* **Commits** never include it: `git add -A` runs, then the sheet is unstaged — `git add -A, never
+  context_<project>.md`, as the desktop puts it.
+
+`test/context.js` checks the template verbatim in the three languages, the "create once, never overwrite" rule,
+the send-once-per-session rule and the git exclusion; the integration test checks that a real task creates the
+sheet and that the bridge receives it.
+
+### Shells
+
+Terminal cards run in a real shell, and which one is not fixed:
+
+| Platform | Shells |
+|---|---|
+| **Windows** | `powershell` (default), `pwsh`, `cmd`, `wsl`, `bash` (Git Bash when installed, otherwise the WSL bash) |
+| **macOS / Linux** | `zsh`, `bash`, `sh`, `fish`, `dash`, `ksh` — or any absolute path |
+
+The order is: the shell the **bridge** names in the `local-exec` request → the shell **you pinned** →
+your **login shell** (`$SHELL`, e.g. `zsh` on macOS, `bash` on most Linux boxes; PowerShell on Windows).
+Pin it with any of:
+
+```
+arenacode --shell zsh
+arenacode config set shell zsh
+/shell              # in the TUI: pick from the shells installed on this machine
 ```
 
-Everything else in the protocol is implemented.
+`sysinfo` reports `shell` and the full `shells` list, and the `!command` prompt line in the TUI runs in the
+same shell as the agent's cards. Commands are passed as a single argv entry (`zsh -lc '<command>'`,
+`cmd.exe /d /s /c '<command>'`, `powershell.exe -NoProfile -NonInteractive -Command '<command>'`), so quotes,
+`$variables` and pipes are never re-quoted on the way through. `test/shell.js` checks every mapping and runs
+real commands through `sh`/`bash`.
 
 ## How it talks to the bridge
 
@@ -319,7 +374,8 @@ release it on the bridge with `keys unbind <ID>`).
   "pc_access": true,
   "device": "",
   "vision": false,
-  "idle_timeout": 180
+  "idle_timeout": 180,
+  "shell": ""
 }
 ```
 
@@ -328,7 +384,7 @@ Node client cannot, so the key sits in that file — keep it readable only by yo
 (`arenacode keys` on the bridge side: `python3 bridge_server.py keys create "laptop CLI"`).
 
 Environment variables override the file: `ARENACODE_URL`, `ARENACODE_KEY`, `ARENACODE_FOLDER`,
-`ARENACODE_CONFIG`.
+`ARENACODE_SHELL`, `ARENACODE_CONFIG`.
 
 ## Troubleshooting
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lardexx/arenacode",
-  "version": "2.9.0",
+  "version": "2.11.0",
   "description": "Terminal client for ArenaCode: talks to an arena-bridge, streams the Agent Mode timeline, and runs local commands, file operations and computer automation on your PC (windows-use.dll on Windows, Xlib/XTest on Linux, osascript on macOS). Node port of the ArenaCode desktop client.",
   "license": "MIT",
   "type": "commonjs",
@@ -20,7 +20,7 @@
     "vendor/"
   ],
   "scripts": {
-    "test": "node test/integration.js && node test/parity.js && node test/automation.js && node test/native.js"
+    "test": "node test/shell.js && node test/context.js && node test/integration.js && node test/parity.js && node test/automation.js && node test/native.js"
   },
   "keywords": [
     "arenacode",

package/src/automation/linux.js

@@ -7,9 +7,9 @@
 const fs = require('node:fs');
 const os = require('node:os');
 const path = require('node:path');
-const zlib = require('node:zlib');
 const { spawn } = require('node:child_process');
 const { lib, fn } = require('./ffi');
+const { encodePng } = require('./png');
 
 const DISPLAY = () => process.env.DISPLAY || ':0';
 
@@ -356,8 +356,7 @@ function pressKeys(combo) {
   requireX();
   const parts = String(combo || '')
     .toLowerCase()
-    .split('+')
-    .map((p) => p.trim())
+    .split(/[\s+]+/)
     .filter(Boolean);
   if (!parts.length) return { ok: false, error: `unreadable key combination: ${combo}` };
   let repeat = 1;
@@ -553,43 +552,6 @@ function resizeWindow(handle, x, y, width, height) {
 
 // ---------------------------------------------------------------- screenshot
 
-function crc32(buf) {
-  let c = 0xffffffff;
-  for (let i = 0; i < buf.length; i += 1) {
-    c ^= buf[i];
-    for (let k = 0; k < 8; k += 1) c = c & 1 ? 0xedb88320 ^ (c >>> 1) : c >>> 1;
-  }
-  return (c ^ 0xffffffff) >>> 0;
-}
-
-function pngChunk(type, data) {
-  const len = Buffer.alloc(4);
-  len.writeUInt32BE(data.length);
-  const body = Buffer.concat([Buffer.from(type, 'ascii'), data]);
-  const crc = Buffer.alloc(4);
-  crc.writeUInt32BE(crc32(body));
-  return Buffer.concat([len, body, crc]);
-}
-
-function encodePng(rgb, width, height) {
-  const raw = Buffer.alloc((width * 3 + 1) * height);
-  for (let y = 0; y < height; y += 1) {
-    raw[y * (width * 3 + 1)] = 0;
-    rgb.copy(raw, y * (width * 3 + 1) + 1, y * width * 3, (y + 1) * width * 3);
-  }
-  const ihdr = Buffer.alloc(13);
-  ihdr.writeUInt32BE(width, 0);
-  ihdr.writeUInt32BE(height, 4);
-  ihdr[8] = 8;
-  ihdr[9] = 2;
-  return Buffer.concat([
-    Buffer.from([0x89, 0x50, 0x4e, 0x47, 0x0d, 0x0a, 0x1a, 0x0a]),
-    pngChunk('IHDR', ihdr),
-    pngChunk('IDAT', zlib.deflateSync(raw, { level: 6 })),
-    pngChunk('IEND', Buffer.alloc(0)),
-  ]);
-}
-
 function screenshot(dest) {
   openDisplay();
   const XGetImage = fn(