feat(tui): handle prompt.submit command in TUI event dispatcher

.github/workflows/nix-hashes.yml

@@ -56,7 +56,7 @@ jobs:
           nix build ".#packages.${SYSTEM}.node_modules_updater" --no-link 2>&1 | tee "$BUILD_LOG" || true
 
           # Extract hash from build log with portability
-          HASH="$(grep -oE 'sha256-[A-Za-z0-9+/=]+' "$BUILD_LOG" | tail -n1 || true)"
+          HASH="$(nix run --inputs-from . nixpkgs#gnugrep -- -oP 'got:\s*\Ksha256-[A-Za-z0-9+/=]+' "$BUILD_LOG" | tail -n1 || true)"
 
           if [ -z "$HASH" ]; then
             echo "::error::Failed to compute hash for ${SYSTEM}"

.github/workflows/publish.yml

@@ -33,7 +33,7 @@ permissions:
 jobs:
   version:
     runs-on: blacksmith-4vcpu-ubuntu-2404
-    if: github.repository == 'anomalyco/opencode'
+    if: contains(fromJSON('["anomalyco/opencode","VibeTechnologies/opencode","vibetechnologies/opencode","dzianisv/opencode"]'), github.repository)
     steps:
       - uses: actions/checkout@v3
         with:
@@ -50,7 +50,7 @@ jobs:
 
       - name: Install OpenCode
         if: inputs.bump || inputs.version
-        run: bun i -g opencode-ai
+        run: bun i -g @vibetechnologies/opencode || bun i -g opencode-ai
 
       - id: version
         run: |
@@ -70,7 +70,7 @@ jobs:
   build-cli:
     needs: version
     runs-on: blacksmith-4vcpu-ubuntu-2404
-    if: github.repository == 'anomalyco/opencode'
+    if: contains(fromJSON('["anomalyco/opencode","VibeTechnologies/opencode","vibetechnologies/opencode","dzianisv/opencode"]'), github.repository)
     steps:
       - uses: actions/checkout@v3
         with:
@@ -443,5 +443,6 @@ jobs:
           AUR_KEY: ${{ secrets.AUR_KEY }}
           GITHUB_TOKEN: ${{ steps.committer.outputs.token }}
           GH_REPO: ${{ needs.version.outputs.repo }}
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN || secrets.NODE_AUTH_TOKEN }}
           NPM_CONFIG_PROVENANCE: false
           LATEST_YML_DIR: /tmp/latest-yml

.github/workflows/review.yml

@@ -4,80 +4,48 @@ on:
   issue_comment:
     types: [created]
 
+concurrency:
+  group: review-${{ github.repository }}-${{ github.event.issue.number }}
+  cancel-in-progress: true
+
 jobs:
-  check-guidelines:
+  review:
     if: |
       github.event.issue.pull_request &&
       startsWith(github.event.comment.body, '/review') &&
       contains(fromJson('["OWNER","MEMBER"]'), github.event.comment.author_association)
     runs-on: blacksmith-4vcpu-ubuntu-2404
     permissions:
+      id-token: write
       contents: read
-      pull-requests: write
+      pull-requests: read
+      issues: read
+    timeout-minutes: 15
     steps:
-      - name: Get PR number
-        id: pr-number
-        run: |
-          if [ "${{ github.event_name }}" = "pull_request_target" ]; then
-            echo "number=${{ github.event.pull_request.number }}" >> $GITHUB_OUTPUT
-          else
-            echo "number=${{ github.event.issue.number }}" >> $GITHUB_OUTPUT
-          fi
-
       - name: Checkout repository
-        uses: actions/checkout@v4
+        uses: actions/checkout@v6
         with:
           fetch-depth: 1
+          persist-credentials: false
 
-      - uses: ./.github/actions/setup-bun
-
-      - name: Install opencode
-        run: curl -fsSL https://opencode.ai/install | bash
-
-      - name: Get PR details
-        id: pr-details
-        run: |
-          gh api /repos/${{ github.repository }}/pulls/${{ steps.pr-number.outputs.number }} > pr_data.json
-          echo "title=$(jq -r .title pr_data.json)" >> $GITHUB_OUTPUT
-          echo "sha=$(jq -r .head.sha pr_data.json)" >> $GITHUB_OUTPUT
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Check PR guidelines compliance
+      - name: Review pull request
+        uses: anomalyco/opencode/github@latest
         env:
-          ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          OPENCODE_PERMISSION: '{ "bash": {  "*": "deny", "gh*": "allow", "gh pr review*": "deny" } }'
-          PR_TITLE: ${{ steps.pr-details.outputs.title }}
-        run: |
-          PR_BODY=$(jq -r .body pr_data.json)
-          opencode run -m anthropic/claude-opus-4-5 "A new pull request has been created: '${PR_TITLE}'
-
-          <pr-number>
-          ${{ steps.pr-number.outputs.number }}
-          </pr-number>
-
-          <pr-description>
-          $PR_BODY
-          </pr-description>
-
-          Please check all the code changes in this pull request against the style guide, also look for any bugs if they exist. Diffs are important but make sure you read the entire file to get proper context. Make it clear the suggestions are merely suggestions and the human can decide what to do
-
-          When critiquing code against the style guide, be sure that the code is ACTUALLY in violation, don't complain about else statements if they already use early returns there. You may complain about excessive nesting though, regardless of else statement usage.
-          When critiquing code style don't be a zealot, we don't like "let" statements but sometimes they are the simplest option, if someone does a bunch of nesting with let, they should consider using iife (see packages/opencode/src/util.iife.ts)
+          OPENCODE_PERMISSION: '{"bash":"deny","edit":"deny","task":"deny"}'
+        with:
+          model: github-copilot/gpt-5.4
+          variant: xhigh
+          prompt: |
+            Review this pull request.
 
-          Use the gh cli to create comments on the files for the violations. Try to leave the comment on the exact line number. If you have a suggested fix include it in a suggestion code block.
-          If you are writing suggested fixes, BE SURE THAT the change you are recommending is actually valid typescript, often I have seen missing closing "}" or other syntax errors.
-          Generally, write a comment instead of writing suggested change if you can help it.
+            Answer these questions:
+            1. Were these changes necessary?
+            2. Is the implementation complete and done in the most optimal way for this repository?
+            3. What, if anything, should still be improved in this branch or pull request?
 
-          Command MUST be like this.
-          \`\`\`
-          gh api \
-            --method POST \
-            -H \"Accept: application/vnd.github+json\" \
-            -H \"X-GitHub-Api-Version: 2022-11-28\" \
-            /repos/${{ github.repository }}/pulls/${{ steps.pr-number.outputs.number }}/comments \
-            -f 'body=[summary of issue]' -f 'commit_id=${{ steps.pr-details.outputs.sha }}' -f 'path=[path-to-file]' -F \"line=[line]\" -f 'side=RIGHT'
-          \`\`\`
+            Review the actual changed code, not just the PR body. Read the full changed files before judging them.
+            Focus on concrete bugs, regressions, missing tests, unnecessary complexity, and obvious maintainability issues in the changed code.
+            Be concise, direct, and specific. Keep this to a single final review response. Do not create inline review comments, do not make code changes, and do not use shell commands.
 
-          Only create comments for actual violations. If the code follows all guidelines, comment on the issue using gh cli: 'lgtm' AND NOTHING ELSE!!!!."
+            If nothing needs attention, say `LGTM` and briefly state why.

.github/workflows/test.yml

@@ -17,6 +17,34 @@ permissions:
   contents: read
 
 jobs:
+  serve-regression:
+    name: serve regression
+    runs-on: blacksmith-4vcpu-ubuntu-2404
+    defaults:
+      run:
+        shell: bash
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Setup Bun
+        uses: ./.github/actions/setup-bun
+
+      - name: Configure git identity
+        run: |
+          git config --global user.email "bot@opencode.ai"
+          git config --global user.name "opencode"
+
+      - name: Run instance lifetime regression
+        working-directory: packages/opencode
+        run: bun test test/project/instance.test.ts -t 'holds refs until async work settles'
+
+      - name: Run detached prompt regression
+        working-directory: packages/opencode
+        run: bun test test/server/session-messages.test.ts -t 'prompt_async keeps an instance ref until detached work finishes'
+
   unit:
     name: unit (${{ matrix.settings.name }})
     strategy:

.gitignore

@@ -1,27 +1,19 @@
-.DS_Store
+# Ignore all hidden files/dirs except .github/
+.*
+!.github/
+
 node_modules
-.worktrees
-.sst
-.env
-.idea
-.vscode
-.codex
 *~
 playground
 tmp
 dist
 ts-dist
-.turbo
-**/.serena
-.serena/
 /result
 refs
 Session.vim
 /opencode.json
 a.out
 target
-.scripts
-.direnv/
 
 # Local dev files
 opencode-dev

.status.md

@@ -0,0 +1,35 @@
+# Status
+
+## TL;DR
+- Continued the scoped `upstram/dev` branch for issue `#46`.
+- Finished cherry-picking the requested fixes only: long shell output handling, MCP idle cleanup/shutdown, browser voice controls, and Recently Active / local recent-session behavior.
+- Resolved the remaining voice-control conflicts and then fixed the follow-up integration bugs exposed by builds and e2e.
+
+## What Was Done
+- Cherry-picked and integrated these requested fixes onto `issue-46-scoped-picks`:
+  - `d7abbab2b` / `61435949d` — long shell tool memory-pressure fixes
+  - `7c1486835` / `fb80ad45c` — shared MCP clients + shutdown cleanup
+  - `42f54f76b` — browser voice controls
+  - `d47229a18` / `e1e015340` / `fda64994a` — Recently Active + local recent sessions
+- Fixed merge fallout/backport drift after the picks:
+- Restored the local install flow that old `main` had:
+  - root `bun run install:local` alias
+  - package-level `build:local` / `sign:local` / `copy:local` / `install:local` / `profile:memory` scripts
+  - `scripts/install-local.sh` and the `packages/opencode/script/*local*.ts` helpers
+  - restored the missing `Flag` import in `packages/opencode/src/mcp/index.ts`
+  - trimmed `packages/opencode/src/cli/cmd/serve.ts` back to the intended shutdown cleanup on `upstram/dev`
+  - made local sidebar sessions follow the active directory/worktree in `packages/app/src/pages/layout/sidebar-workspace.tsx`
+  - made sidebar hover-prefetch use the `preview` query path end-to-end by updating the session route contract and regenerating the JS SDK
+  - hardened e2e project seeding in `packages/app/e2e/actions.ts`
+
+## Current Issue
+- No known blocker right now.
+- The scoped branch is building and the targeted tests are passing.
+
+## Validation
+- `bun install`
+- `cd packages/opencode && bun run build`
+- `cd packages/app && bun run build`
+- `cd packages/opencode && bun test test/server/global-session-route.test.ts test/server/static-app.test.ts test/server/global-session-list.test.ts test/server/session-list.test.ts test/pty/pty-session.test.ts`
+- `cd packages/app && bun test --preload ./happydom.ts ./src/utils/runtime-adapters.test.ts`
+- `cd packages/app && bun run test:e2e:local -- e2e/prompt/prompt-voice.spec.ts e2e/sidebar/sidebar-recent-prefetch.spec.ts e2e/sidebar/sidebar-session-links.spec.ts`

AGENTS.md

@@ -3,6 +3,16 @@
 - The default branch in this repo is `dev`.
 - Local `main` ref may not exist; use `dev` or `origin/dev` for diffs.
 - Prefer automation: execute requested actions without confirmation unless blocked by missing info or safety/irreversibility.
+- App e2e note: `bun test:e2e` expects a backend at `127.0.0.1:4096`; use `bun test:e2e:local -- -- <spec>` when running tests in isolation.
+
+## Devx
+
+- If a task has an upstream issue (for example in `anomalyco/opencode`), keep that issue updated while working.
+- When any commit/PR/merge relates to an upstream issue, add an upstream issue comment with:
+  - what changed
+  - commit SHA and PR link
+  - current status (in progress, merged, or blocked)
+- Do not wait until the end of the task; post updates as soon as relevant commits or merges happen.
 
 ## Style Guide
 
@@ -123,6 +133,28 @@ const table = sqliteTable("session", {
 - Test actual implementation, do not duplicate logic into tests
 - Tests cannot run from repo root (guard: `do-not-run-tests-from-root`); run from package dirs like `packages/opencode`.
 
+## Memory Panic Triage
+
+If the user reports a panic, OOM, runaway RSS, or unexplained restarts, analyze memory artifacts before guessing.
+
+1. Capture the current state.
+   Run the relevant package-scoped checks first, such as `bun run --cwd packages/opencode profile:memory:wait` for a waiting server or `bun run --cwd packages/opencode profile:memory:workload` for a synthetic reproduction.
+2. Inspect the durable artifacts under `~/.local/share/opencode/log`.
+   Start with `dev.log`, the newest `memory-*.ndjson`, and the newest directories in `~/.local/share/opencode/log/memory/`.
+3. Read the snapshot files in order.
+   `sample.json` shows RSS, heap, PTY count, session counts, and instance-cache pressure.
+   `meta.json` shows why the snapshot was taken and the threshold or trigger state.
+   `ps.txt` shows child-process footprint.
+   On macOS, also inspect `vmmap.txt` and `sample.txt`.
+4. Open `heap.heapsnapshot` only after you know the spike is heap-related.
+   Use Chrome DevTools Memory tooling to inspect retained objects and dominators.
+5. Check disk pressure alongside memory pressure.
+   Inspect `~/.local/share/opencode/worktree`, `~/.local/share/opencode/tool-output`, and `~/.local/share/opencode/log` so you do not misdiagnose a disk-exhaustion crash as a heap leak.
+6. Preserve evidence in the issue or PR.
+   Record exact sizes, timestamps, active session counts, and the snapshot trigger reason.
+
+Do not generate repeated snapshots blindly. Retention keeps only the newest `2` heap snapshot directories, so if an older capture matters, attach or summarize it before reproducing again.
+
 ## Type Checking
 
 - Always run `bun typecheck` from package directories (e.g., `packages/opencode`), never `tsc` directly.