release: v2.1.2

fix(session-notification): Replace blocking MessageBox with native toast on Windows (#62 )
The previous Windows implementation used System.Windows.Forms.MessageBox which displays a blocking modal dialog requiring user interaction. This replaces it with the native Windows.UI.Notifications.ToastNotificationManager API (Windows 10+) which shows a non-intrusive toast notification in the corner, consistent with macOS and Linux behavior. - Uses native Toast API (no external dependencies like BurntToast) - Non-blocking: notification auto-dismisses - Graceful degradation: silently fails on older Windows versions - Fix escaping for each platform (PowerShell: '' for quotes, AppleScript: backslash)
2025-12-15 23:58:46 +00:00 · 2025-12-16 08:54:55 +09:00 · 2025-12-15 16:22:13 +00:00 · 2025-12-16 01:02:49 +09:00 · 2025-12-16 01:02:39 +09:00 · 2025-12-15 23:54:59 +09:00
52 changed files with 3777 additions and 779 deletions
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -1,7 +1,7 @@
 # PROJECT KNOWLEDGE BASE

-**Generated:** 2025-12-14T17:16:30+09:00
-**Commit:** 7f27fbc
+**Generated:** 2025-12-15T22:57:00+09:00
+**Commit:** cea64e4
 **Branch:** master

 ## OVERVIEW
@@ -14,10 +14,10 @@ OpenCode plugin implementing Claude Code/AmpCode features. Multi-model agent orc
 oh-my-opencode/
 ├── src/
 │   ├── agents/        # AI agents (OmO, oracle, librarian, explore, frontend, document-writer, multimodal-looker)
-│   ├── hooks/         # 19 lifecycle hooks (comment-checker, rules-injector, keyword-detector, etc.)
-│   ├── tools/         # LSP (11), AST-Grep, Grep, background-task, glob, look-at, skill, slashcommand
+│   ├── hooks/         # 21 lifecycle hooks (comment-checker, rules-injector, keyword-detector, etc.)
+│   ├── tools/         # LSP (11), AST-Grep, Grep, Glob, background-task, look-at, skill, slashcommand, interactive-bash, call-omo-agent
 │   ├── mcp/           # MCP servers (context7, websearch_exa, grep_app)
-│   ├── features/      # Terminal features, Claude Code loaders (agent, command, skill, mcp, session-state)
+│   ├── features/      # Terminal, Background agent, Claude Code loaders (agent, command, skill, mcp, session-state), hook-message-injector
 │   ├── config/        # Zod schema, TypeScript types
 │   ├── auth/          # Google Antigravity OAuth
 │   ├── shared/        # Utilities (deep-merge, pattern-matcher, logger, etc.)
@@ -40,6 +40,8 @@ oh-my-opencode/
 | Google OAuth | `src/auth/antigravity/` | OAuth plugin for Google models |
 | Config schema | `src/config/schema.ts` | Zod schema, run `bun run build:schema` after changes |
 | Claude Code compat | `src/features/claude-code-*-loader/` | Command, skill, agent, mcp loaders |
+| Background agents | `src/features/background-agent/` | manager.ts for task management |
+| Interactive terminal | `src/tools/interactive-bash/` | tmux session management |

 ## CONVENTIONS

--- a/README.ja.md
+++ b/README.ja.md
@@ -0,0 +1,702 @@
+<!-- <CENTERED SECTION FOR GITHUB DISPLAY> -->
+
+<div align="center">
+
+[![Oh My OpenCode](./.github/assets/hero.jpg)](https://github.com/code-yeongyu/oh-my-opencode#oh-my-opencode)
+
+[![Preview](./.github/assets/preview.png)](https://github.com/code-yeongyu/oh-my-opencode#oh-my-opencode)
+
+
+</div>
+
+> `oh-my-opencode` をインストールして、ドーピングしたかのようにコーディングしましょう。バックグラウンドでエージェントを走らせ、oracle、librarian、frontend engineer のような専門エージェントを呼び出してください。丹精込めて作られた LSP/AST ツール、厳選された MCP、そして完全な Claude Code 互換レイヤーを、たった一行で手に入れましょう。
+
+<div align="center">
+
+[![GitHub Release](https://img.shields.io/github/v/release/code-yeongyu/oh-my-opencode?color=369eff&labelColor=black&logo=github&style=flat-square)](https://github.com/code-yeongyu/oh-my-opencode/releases)
+[![GitHub Contributors](https://img.shields.io/github/contributors/code-yeongyu/oh-my-opencode?color=c4f042&labelColor=black&style=flat-square)](https://github.com/code-yeongyu/oh-my-opencode/graphs/contributors)
+[![GitHub Forks](https://img.shields.io/github/forks/code-yeongyu/oh-my-opencode?color=8ae8ff&labelColor=black&style=flat-square)](https://github.com/code-yeongyu/oh-my-opencode/network/members)
+[![GitHub Stars](https://img.shields.io/github/stars/code-yeongyu/oh-my-opencode?color=ffcb47&labelColor=black&style=flat-square)](https://github.com/code-yeongyu/oh-my-opencode/stargazers)
+[![GitHub Issues](https://img.shields.io/github/issues/code-yeongyu/oh-my-opencode?color=ff80eb&labelColor=black&style=flat-square)](https://github.com/code-yeongyu/oh-my-opencode/issues)
+[![License](https://img.shields.io/badge/license-MIT-white?labelColor=black&style=flat-square)](https://github.com/code-yeongyu/oh-my-opencode/blob/master/LICENSE)
+
+[English](README.md) | [한국어](README.ko.md) | [日本語](README.ja.md)
+
+</div>
+
+<!-- </CENTERED SECTION FOR GITHUB DISPLAY> -->
+
+## 目次
+
+- [Oh My OpenCode](#oh-my-opencode)
+  - [この Readme は読まなくていいです](#この-readme-は読まなくていいです)
+    - [エージェントの時代ですから](#エージェントの時代ですから)
+    - [10分の投資で OhMyOpenCode が可能にすること](#10分の投資で-ohmyopencode-が可能にすること)
+  - [インストール](#インストール)
+    - [人間の方へ](#人間の方へ)
+    - [LLM エージェントの方へ](#llm-エージェントの方へ)
+    - [ステップ 1: OpenCode インストール確認](#ステップ-1-opencode-インストール確認)
+    - [ステップ 2: oh-my-opencode プラグイン設定](#ステップ-2-oh-my-opencode-プラグイン設定)
+    - [ステップ 3: 設定確認](#ステップ-3-設定確認)
+    - [ステップ 4: 認証情報の設定](#ステップ-4-認証情報の設定)
+      - [4.1 Anthropic (Claude)](#41-anthropic-claude)
+      - [4.2 Google Gemini (Antigravity OAuth)](#42-google-gemini-antigravity-oauth)
+      - [4.3 OpenAI (ChatGPT Plus/Pro)](#43-openai-chatgpt-pluspro)
+      - [4.3.1 モデル設定](#431-モデル設定)
+    - [⚠️ 注意](#️-注意)
+  - [機能](#機能)
+    - [Agents: あなたの新しいチームメイト](#agents-あなたの新しいチームメイト)
+    - [バックグラウンドエージェント: 本当のチームのように働く](#バックグラウンドエージェント-本当のチームのように働く)
+    - [ツール: 同僚にはもっと良い道具を](#ツール-同僚にはもっと良い道具を)
+      - [なぜあなただけ IDE を使っているのですか？](#なぜあなただけ-ide-を使っているのですか)
+      - [Context is all you need.](#context-is-all-you-need)
+      - [マルチモーダルを活用し、トークンは節約する](#マルチモーダルを活用しトークンは節約する)
+      - [止まらないエージェントループ](#止まらないエージェントループ)
+    - [Claude Code 互換性: さらば Claude Code、ようこそ OpenCode](#claude-code-互換性-さらば-claude-codeようこそ-opencode)
+      - [Hooks 統合](#hooks-統合)
+      - [設定ローダー](#設定ローダー)
+      - [データストレージ](#データストレージ)
+      - [互換性トグル](#互換性トグル)
+    - [エージェントのためだけでなく、あなたのために](#エージェントのためだけでなくあなたのために)
+  - [設定](#設定)
+    - [Google Auth](#google-auth)
+    - [Agents](#agents)
+    - [MCPs](#mcps)
+    - [LSP](#lsp)
+  - [作者のノート](#作者のノート)
+  - [注意](#注意)
+
+# Oh My OpenCode
+
+oMoMoMoMoMo···
+
+
+[Claude Code](https://www.claude.com/product/claude-code) は素晴らしいですよね。
+でも、もしあなたがハッカーなら、[OpenCode](https://github.com/sst/opencode) と恋に落ちることになるでしょう。
+
+- 無限に拡張可能で、無限にカスタマイズ可能です。
+- 画面のチラつき（フリッカー）がありません。
+- 編集するファイルに合わせて [LSP](https://opencode.ai/docs/lsp/)、[Linter、Formatter](https://opencode.ai/docs/formatters/) が自動的に有効化され、すべて調整可能です。
+- 複数のモデルを組み合わせて使用でき、**用途に応じてオーケストレーションできます。**
+- 機能が豊富で、美しい。ターミナルが描画に苦しむことはありません。高パフォーマンスです。
+
+Windows から Linux に初めて乗り換えた時のこと、自分の思い通りに設定して興奮したあの感覚を覚えていますか？
+そんな魔法が失われたかのような今の時代に、OpenCode はその感覚を取り戻してくれます。
+コーディングとコンピュータを愛するあなたにとって、OpenCode はまさに「Windows の後の Linux」のような瞬間になるはずです。
+
+**しかし問題は、学ぶべきことが多すぎること、複雑であること、そしてあなたの時間は高価だということです。**
+
+私がその問題を解決しました。
+あなたがハッカーでなくても構いません。数分の投資で、スキルと生産性を何倍にもブーストしてください。
+このドキュメントをエージェントに渡して、セットアップを任せましょう。
+
+## この Readme は読まなくていいです
+
+### エージェントの時代ですから
+- **ただこのリンクを Claude Code / AmpCode / Factory Droid / Cursor に貼り付けて、説明を求めてください。**
+  - なぜこれが良いのか、単なるボイラープレートではないのか、具体的に何が良くなるのか聞いてみてください。
+  - もしあなたが LLM エージェントなら、このプロジェクトによって今すぐ何が可能になるのか、ユーザーに説明してください。
+
+### 10分の投資で OhMyOpenCode が可能にすること
+
+インストールするだけで、エージェントは以下のようなワークフローで働けるようになります：
+
+1. バックグラウンドタスクとして Gemini 3 Pro にフロントエンドを書かせている間に、Claude Opus 4.5 がバックエンドを作成し、デバッグで詰まったら GPT 5.2 に助けを求めます。フロントエンドの実装完了報告が来たら、それを検証して出荷します。
+2. 何か調べる必要があれば、公式ドキュメント、コードベースの全履歴、GitHub に公開されている実装例まで徹底的に調査します。単なる grep だけでなく、内蔵された LSP ツールや AST-Grep まで駆使します。
+3. LLM に仕事を任せる際、コンテキスト管理の心配はもう不要です。私がやります。
+    - OhMyOpenCode は複数のエージェントを積極的に活用し、コンテキストの負荷を軽減します。
+    - **あなたのエージェントは今や開発チームのリードです。あなたは AI マネージャーです。**
+4. 頼んだ仕事が完了するまで止まりません。
+5. このプロジェクトについて深く知りたくない？大丈夫です。ただ 'ultrathink' と入力してください。
+
+注：これをインストールしたからといって、魔法のように OpenCode がこのように動作するわけではありません。上記の説明は「こういう使い方もできる」という例示です。単にあなたのエージェントに優秀な同僚を紹介し、強力な道具を渡すだけです。彼らに協力しろと指示すれば、協力するでしょう。
+すべてはあなたが完全にコントロールできます。
+ultrathink を通じて自動的に動作させることもできますが、必須ではありません。このプロジェクトはあなたの AI エージェントのワークフローを強制しません。
+ただ、あなたのエージェントに素晴らしい同僚を紹介し、より良い道具を手に持たせるだけです。
+
+- 複雑で巨大なタスクを投げてください。
+  - プロンプトに "ultrawork" というキーワードを入れるだけで、すべて自動的に処理します。
+
+## インストール
+
+
+### 人間の方へ
+
+面倒な作業は LLM エージェントに任せましょう。このリンクをコピーして貼り付け、インストールと設定をお願いしてください。
+
+### LLM エージェントの方へ
+
+<details>
+<summary>LLM エージェント向け手順（クリックして展開）</summary>
+
+あなたがユーザーの oh-my-opencode 設定を支援する LLM エージェントなら、以下の手順に従ってください：
+
+
+### ステップ 1: OpenCode インストール確認
+
+```bash
+if command -v opencode &> /dev/null; then
+    echo "OpenCode $(opencode --version) はインストールされています"
+else
+    echo "OpenCode がインストールされていません。先にインストールしてください。"
+    echo "参照: https://opencode.ai/docs"
+fi
+```
+
+OpenCode がインストールされていない場合は、[OpenCode インストールガイド](https://opencode.ai/docs)を確認し、インストールを進めてください。コンテキストを節約するため、サブエージェントを呼び出してインストールを行わせ、その結果を報告させるように案内してください。
+
+### ステップ 2: oh-my-opencode プラグイン設定
+
+```bash
+mkdir -p ~/.config/opencode
+
+if [ -f ~/.config/opencode/opencode.json ]; then
+    # 既存の設定ファイルがある場合: jq または python で plugin を追加
+    if command -v jq &> /dev/null; then
+        jq '.plugin = ((.plugin // []) + ["oh-my-opencode"] | unique)' \
+            ~/.config/opencode/opencode.json > /tmp/oc.json && \
+            mv /tmp/oc.json ~/.config/opencode/opencode.json
+    else
+        echo "~/.config/opencode/opencode.json の plugin 配列に \"oh-my-opencode\" を追加してください"
+    fi
+else
+    # 新しい設定ファイル作成
+    echo '{"plugin":["oh-my-opencode"]}' > ~/.config/opencode/opencode.json
+fi
+```
+
+### ステップ 3: 設定確認
+
+```bash
+opencode --version  # 1.0.132 以上であること
+cat ~/.config/opencode/opencode.json  # plugin 配列に "oh-my-opencode" が含まれていること
+```
+
+### ステップ 4: 認証情報の設定
+
+plugin に oh-my-opencode を追加したら、tmux を使用してユーザーの認証設定を進めてください。以下の手順をすべて完了する必要があります。
+
+#### 4.1 Anthropic (Claude)
+
+```bash
+opencode auth login
+# Provider: Anthropic を選択
+# Login method: Claude Pro/Max を選択
+# ユーザーにブラウザでの OAuth フロー完了を案内してください
+# 完了まで待機
+# 成功を確認し、ユーザーに報告
+```
+
+#### 4.2 Google Gemini (Antigravity OAuth)
+
+まず、`~/.config/opencode/oh-my-opencode.json` で Google auth を有効にします：
+
+```json
+{
+  "google_auth": true
+}
+```
+
+その後、認証を行います：
+
+```bash
+opencode auth login
+# Provider: Google を選択
+# Login method: OAuth with Google (Antigravity) を選択
+# ユーザーにブラウザでの OAuth フロー完了を案内
+# 完了まで待機
+# 成功を確認し、ユーザーに報告
+```
+
+#### 4.3 OpenAI (ChatGPT Plus/Pro)
+
+まず、opencode-openai-codex-auth プラグインを追加します：
+
+```json
+{
+  "plugin": [
+    "oh-my-opencode",
+    "opencode-openai-codex-auth@4.1.0"
+  ]
+}
+```
+
+**重要**: 現在、公式 npm パッケージに 400 エラー (`"No tool call found for function call output with call_id"`) を引き起こすバグがあります。修正版がリリースされるまでは、**ホットフィックスブランチの使用を推奨します**。`~/.config/opencode/package.json` を修正してください：
+
+```json
+{
+  "dependencies": {
+    "opencode-openai-codex-auth": "code-yeongyu/opencode-openai-codex-auth#fix/orphaned-function-call-output-with-tools"
+  }
+}
+```
+
+その後、`cd ~/.config/opencode && bun i` を実行してください。`opencode.json` ではバージョン指定なしで `"opencode-openai-codex-auth"` として使用します（`@4.1.0` は除外）。
+
+#### 4.3.1 モデル設定
+`opencode.json` に完全なモデル設定も構成する必要があります。
+[opencode-openai-codex-auth ドキュメント](https://github.com/numman-ali/opencode-openai-codex-auth)を読み、[`config/full-opencode.json`](https://github.com/numman-ali/opencode-openai-codex-auth/blob/main/config/full-opencode.json) から provider/models 設定をコピーして、ユーザーの既存のセットアップを壊さないよう慎重にマージしてください。
+
+その後、認証を行います：
+
+```bash
+opencode auth login
+# Provider: OpenAI を選択
+# Login method: ChatGPT Plus/Pro (Codex Subscription) を選択
+# ユーザーにブラウザでの OAuth フロー完了を案内
+# 完了まで待機
+# 成功を確認し、ユーザーに報告
+```
+
+
+### ⚠️ 注意
+
+**ユーザーが明示的に要求しない限り、モデル設定を変更したり、機能（エージェント、フック、MCP）を無効化しないでください。**
+
+プラグインはデフォルトで完璧に動作します。推奨される `google_auth: true` 設定を除き、明示的な要求なしに他の設定を変更したり機能をオフにしないでください。
+
+</details>
+
+
+## 機能
+
+### Agents: あなたの新しいチームメイト
+
+- **OmO** (`anthropic/claude-opus-4-5`): **デフォルトエージェントです。** OpenCode のための強力な AI オーケストレーターです。専門のサブエージェントを活用して、複雑なタスクを計画、委任、実行します。バックグラウンドタスクへの委任と Todo ベースのワークフローを重視します。最大の推論能力を発揮するため、Claude Opus 4.5 と拡張思考 (32k token budget) を使用します。
+- **oracle** (`openai/gpt-5.2`): アーキテクチャ、コードレビュー、戦略立案のための専門アドバイザー。GPT-5.2 の卓越した論理的推論と深い分析能力を活用します。AmpCode からインスピレーションを得ました。
+- **librarian** (`anthropic/claude-sonnet-4-5`): マルチリポジトリ分析、ドキュメント検索、実装例の調査を担当。Claude Sonnet 4.5 を使用して、深いコードベース理解と GitHub リサーチ、根拠に基づいた回答を提供します。AmpCode からインスピレーションを得ました。
+- **explore** (`opencode/grok-code`): 高速なコードベース探索、ファイルパターンマッチング。Claude Code は Haiku を使用しますが、私たちは Grok を使います。現在無料であり、極めて高速で、ファイル探索タスクには十分な知能を備えているからです。Claude Code からインスピレーションを得ました。
+- **frontend-ui-ux-engineer** (`google/gemini-3-pro-preview`): 開発者に転身したデザイナーという設定です。素晴らしい UI を作ります。美しく独創的な UI コードを生成することに長けた Gemini を使用します。
+- **document-writer** (`google/gemini-3-pro-preview`): テクニカルライティングの専門家という設定です。Gemini は文筆家であり、流れるような文章を書きます。
+- **multimodal-looker** (`google/gemini-2.5-flash`): 視覚コンテンツ解釈のための専門エージェント。PDF、画像、図表を分析して情報を抽出します。
+
+メインエージェントはこれらを自動的に呼び出しますが、明示的に呼び出すことも可能です：
+
+```
+Ask @oracle to review this design and propose an architecture
+（@oracle にこの設計をレビューさせ、アーキテクチャを提案させて）
+Ask @librarian how this is implemented—why does the behavior keep changing?
+（@librarian にこれがどう実装されているか聞いて、なぜ挙動が変わり続けるのか教えて）
+Ask @explore for the policy on this feature
+（@explore にこの機能のポリシーを聞いて）
+```
+
+エージェントのモデル、プロンプト、権限は `oh-my-opencode.json` でカスタマイズ可能です。詳細は [設定](#設定) を参照してください。
+
+### バックグラウンドエージェント: 本当のチームのように働く
+
+上記のエージェントたちを、一瞬たりとも休ませることなく働かせられたらどうでしょうか？
+
+- GPT にデバッグさせておいて、Claude が別のアプローチで根本原因を探るワークフロー
+- Gemini がフロントエンドを書いている間に、Claude がバックエンドを書くワークフロー
+- 大量の並列探索を開始し、その部分は一旦置いておいて実装を進め、探索結果が出たらそれを使って仕上げるワークフロー
+
+これらのワークフローが OhMyOpenCode では可能です。
+
+サブエージェントをバックグラウンドで実行できます。メインエージェントはタスクが完了すると通知を受け取ります。必要であれば結果を待つこともできます。
+
+**エージェントが、あなたのチームのように働くようにしましょう。**
+
+### ツール: 同僚にはもっと良い道具を
+
+#### なぜあなただけ IDE を使っているのですか？
+
+シンタックスハイライト、自動補完、リファクタリング、ナビゲーション、分析…そして今やエージェントがコードを書く時代です。
+
+**なぜあなただけがそれらのツールを使っているのですか？**
+**エージェントにそれらを使わせれば、彼らはレベルアップします。**
+
+[OpenCode は LSP を提供していますが](https://opencode.ai/docs/lsp/)、あくまで分析用です。
+
+あなたがエディタで使っているその機能、他のエージェントは触ることができません。
+最高の同僚に最高の道具を渡してください。これでリファクタリングも、ナビゲーションも、分析も、エージェントが適切に行えるようになります。
+
+- **lsp_hover**: その位置の型情報、ドキュメント、シグネチャを取得
+- **lsp_goto_definition**: シンボル定義へジャンプ
+- **lsp_find_references**: ワークスペース全体で使用箇所を検索
+- **lsp_document_symbols**: ファイルのシンボルアウトラインを取得
+- **lsp_workspace_symbols**: プロジェクト全体から名前でシンボルを検索
+- **lsp_diagnostics**: ビルド前にエラー/警告を取得
+- **lsp_servers**: 利用可能な LSP サーバー一覧
+- **lsp_prepare_rename**: 名前変更操作の検証
+- **lsp_rename**: ワークスペース全体でシンボル名を変更
+- **lsp_code_actions**: 利用可能なクイックフィックス/リファクタリングを取得
+- **lsp_code_action_resolve**: コードアクションを適用
+- **ast_grep_search**: AST 認識コードパターン検索 (25言語対応)
+- **ast_grep_replace**: AST 認識コード置換
+
+#### Context Is All You Need
+- **Directory AGENTS.md / README.md Injector**: ファイルを読み込む際、`AGENTS.md` と `README.md` の内容を自動的に注入します。ファイルディレクトリからプロジェクトルートまで遡り、パス上の **すべて** の `AGENTS.md` ファイルを収集します。ネストされたディレクトリごとの指示をサポートします：
+  ```
+  project/
+  ├── AGENTS.md              # プロジェクト全体のコンテキスト
+  ├── src/
+  │   ├── AGENTS.md          # src 専用コンテキスト
+  │   └── components/
+  │       ├── AGENTS.md      # コンポーネント専用コンテキスト
+  │       └── Button.tsx     # このファイルを読むと上記3つの AGENTS.md がすべて注入される
+  ```
+  `Button.tsx` を読むと、順序通りに注入されます：`project/AGENTS.md` → `src/AGENTS.md` → `components/AGENTS.md`。各ディレクトリのコンテキストはセッションごとに一度だけ注入されます。
+- **Conditional Rules Injector**: すべてのルールが常に必要なわけではありません。条件に一致する場合にのみ、`.claude/rules/` ディレクトリからルールを注入します。
+  - ファイルディレクトリからプロジェクトルートまで上方向に探索し、`~/.claude/rules/` (ユーザー) パスも含みます。
+  - `.md` および `.mdc` ファイルをサポートします。
+  - Frontmatter の `globs` フィールド（glob パターン）に基づいてマッチングします。
+  - 常に適用されるべきルールのために `alwaysApply: true` オプションをサポートします。
+  - ルールファイルの例：
+    ```markdown
+    ---
+    globs: ["*.ts", "src/**/*.js"]
+    description: "TypeScript/JavaScript coding rules"
+    ---
+    - Use PascalCase for interface names
+    - Use camelCase for function names
+    ```
+- **Online**: プロジェクトのルールがすべてではありません。拡張機能のための内蔵 MCP を提供します：
+  - **context7**: ライブラリの最新公式ドキュメントを取得
+  - **websearch_exa**: Exa AI を活用したリアルタイムウェブ検索
+  - **grep_app**: 数百万の公開 GitHub リポジトリから超高速コード検索（実装例を探すのに最適）
+
+#### マルチモーダルを活用し、トークンは節約する
+
+AmpCode からインスピレーションを受けた look_at ツールを、OhMyOpenCode でも提供します。
+エージェントが巨大なファイルを直接読んでコンテキストを浪費する代わりに、内部的に別のエージェントを活用して必要な情報だけを抽出します。
+
+#### 止まらないエージェントループ
+- 内蔵 grep、glob ツールを置き換えます。デフォルトの実装にはタイムアウトがなく、無限にハングする可能性があります。
+
+
+### Claude Code 互換性: さらば Claude Code、ようこそ OpenCode
+
+Oh My OpenCode には Claude Code 互換レイヤーが存在します。
+Claude Code を使用していた場合、既存の設定がそのまま動作します。
+
+#### Hooks 統合
+
+Claude Code の `settings.json` フックシステムを通じてカスタムスクリプトを実行します。
+Oh My OpenCode は以下の場所からフックを読み込んで実行します：
+
+- `~/.claude/settings.json` (ユーザー)
+- `./.claude/settings.json` (プロジェクト)
+- `./.claude/settings.local.json` (ローカル、git-ignored)
+
+サポートされるフックイベント：
+- **PreToolUse**: ツール実行前に実行。ブロックしたり、ツール入力を修正したりできます。
+- **PostToolUse**: ツール実行後に実行。警告やコンテキストを追加できます。
+- **UserPromptSubmit**: ユーザーがプロンプトを送信した時に実行。ブロックしたり、メッセージを注入したりできます。
+- **Stop**: セッションがアイドル状態になった時に実行。フォローアップのプロンプトを注入できます。
+
+`settings.json` の例：
+```json
+{
+  "hooks": {
+    "PostToolUse": [
+      {
+        "matcher": "Write|Edit",
+        "hooks": [{ "type": "command", "command": "eslint --fix $FILE" }]
+      }
+    ]
+  }
+}
+```
+
+#### 設定ローダー
+
+**Command Loader**: 4つのディレクトリからマークダウンベースのスラッシュコマンドをロードします：
+- `~/.claude/commands/` (ユーザー)
+- `./.claude/commands/` (プロジェクト)
+- `~/.config/opencode/command/` (opencode グローバル)
+- `./.opencode/command/` (opencode プロジェクト)
+
+**Skill Loader**: `SKILL.md` があるディレクトリベースのスキルをロードします：
+- `~/.claude/skills/` (ユーザー)
+- `./.claude/skills/` (プロジェクト)
+
+**Agent Loader**: マークダウンファイルからカスタムエージェント定義をロードします：
+- `~/.claude/agents/*.md` (ユーザー)
+- `./.claude/agents/*.md` (プロジェクト)
+
+**MCP Loader**: `.mcp.json` ファイルから MCP サーバー設定をロードします：
+- `~/.claude/.mcp.json` (ユーザー)
+- `./.mcp.json` (プロジェクト)
+- `./.claude/.mcp.json` (ローカル)
+- 環境変数展開をサポート (`${VAR}` 構文)
+
+#### データストレージ
+
+**Todo 管理**: セッションの Todo が `~/.claude/todos/` に Claude Code 互換形式で保存されます。
+
+**Transcript**: セッションのアクティビティが `~/.claude/transcripts/` に JSONL 形式で記録され、再生や分析が可能です。
+
+#### 互換性トグル
+
+特定の Claude Code 互換機能を無効にするには、`claude_code` 設定オブジェクトを使用できます：
+
+```json
+{
+  "claude_code": {
+    "mcp": false,
+    "commands": false,
+    "skills": false,
+    "agents": false,
+    "hooks": false
+  }
+}
+```
+
+| トグル     | `false` の場合、ロードが無効になるパス                                                | 影響を受けないもの                                    |
+| ---------- | ------------------------------------------------------------------------------------- | ----------------------------------------------------- |
+| `mcp`      | `~/.claude/.mcp.json`, `./.mcp.json`, `./.claude/.mcp.json`                           | 内蔵 MCP (context7, websearch_exa)                    |
+| `commands` | `~/.claude/commands/*.md`, `./.claude/commands/*.md`                                  | `~/.config/opencode/command/`, `./.opencode/command/` |
+| `skills`   | `~/.claude/skills/*/SKILL.md`, `./.claude/skills/*/SKILL.md`                          | -                                                     |
+| `agents`   | `~/.claude/agents/*.md`, `./.claude/agents/*.md`                                      | 内蔵エージェント (oracle, librarian 等)               |
+| `hooks`    | `~/.claude/settings.json`, `./.claude/settings.json`, `./.claude/settings.local.json` | -                                                     |
+
+すべてのトグルはデフォルトで `true` (有効) です。完全な Claude Code 互換性を望む場合は `claude_code` オブジェクトを省略してください。
+
+### エージェントのためだけでなく、あなたのために
+
+エージェントが活躍すれば、あなたも幸せになります。ですが、私はあなた自身も助けたいのです。
+
+- **Keyword Detector**: プロンプト内のキーワードを自動検知して専門モードを有効化します：
+  - `ultrawork` / `ulw`: 並列エージェントオーケストレーションによる最大パフォーマンスモード
+  - `search` / `find` / `찾아` / `検索`: 並列 explore/librarian エージェントによる検索最大化
+  - `analyze` / `investigate` / `분석` / `調査`: 多段階の専門家相談による深層分析モード
+- **Todo Continuation Enforcer**: エージェントが停止する前にすべての TODO 項目を完了するように強制します。LLM の「中途半端に終わる」癖を防止します。
+- **Comment Checker**: 学習データの影響でしょうか、LLM はコメントが多すぎます。無駄なコメントを書かないようリマインドします。BDD パターン、指示子、docstring などの有効なコメントは賢く除外し、それ以外のコメントについては正当性を求め、クリーンなコードを維持させます。
+- **Think Mode**: 拡張思考 (Extended Thinking) が必要な状況を自動検知してモードを切り替えます。「深く考えて (think deeply)」「ultrathink」といった表現を検知すると、推論能力を最大化するようモデル設定を動的に調整します。
+- **Context Window Monitor**: [Context Window Anxiety Management](https://agentic-patterns.com/patterns/context-window-anxiety-management/) パターンを実装しています。
+  - 使用率が 70% を超えると、まだ余裕があることをエージェントにリマインドし、焦って雑な仕事をすることを防ぎます。
+- **Agent Usage Reminder**: 検索ツールを直接呼び出す際、バックグラウンドタスクを通じた専門エージェントの活用を推奨するリマインダーを表示します。
+- **Anthropic Auto Compact**: Claude モデルがトークン制限に達すると、自動的にセッションを要約・圧縮します。手動での介入は不要です。
+- **Session Recovery**: セッションエラー（ツールの結果欠落、thinking ブロックの問題、空のメッセージなど）から自動復旧します。セッションが途中でクラッシュすることはありません。もしクラッシュしても復旧します。
+- **Auto Update Checker**: oh-my-opencode の新バージョンがリリースされると通知します。
+- **Startup Toast**: OhMyOpenCode ロード時にウェルカムメッセージを表示します。セッションを正しく始めるための、ささやかな "oMoMoMo" です。
+- **Background Notification**: バックグラウンドエージェントのタスクが完了すると通知を受け取ります。
+- **Session Notification**: エージェントがアイドル状態になると OS 通知を送ります。macOS、Linux、Windows で動作します—エージェントが入力を待っている時を見逃しません。
+- **Empty Task Response Detector**: Task ツールが空の応答を返すと検知します。既に空の応答が返ってきているのに、いつまでも待ち続ける状況を防ぎます。
+- **Grep Output Truncator**: grep は山のようなテキストを返すことがあります。残りのコンテキストウィンドウに応じて動的に出力を切り詰めます—50% の余裕を維持し、最大 50k トークンに制限します。
+- **Tool Output Truncator**: 同じ考え方をより広範囲に適用します。Grep、Glob、LSP ツール、AST-grep の出力を切り詰めます。一度の冗長な検索がコンテキスト全体を食いつぶすのを防ぎます。
+
+## 設定
+
+こだわりが強く反映された設定ですが、好みに合わせて調整可能です。
+
+設定ファイルの場所（優先順）：
+1. `.opencode/oh-my-opencode.json` (プロジェクト)
+2. `~/.config/opencode/oh-my-opencode.json` (ユーザー)
+
+スキーマ自動補完がサポートされています：
+
+```json
+{
+  "$schema": "https://raw.githubusercontent.com/code-yeongyu/oh-my-opencode/master/assets/oh-my-opencode.schema.json"
+}
+```
+
+### Google Auth
+
+Google Gemini モデルのための内蔵 Antigravity OAuth を有効化します：
+
+```json
+{
+  "google_auth": true
+}
+```
+
+有効化すると、`opencode auth login` 実行時に Google プロバイダーで "OAuth with Google (Antigravity)" ログインオプションが表示されます。
+
+### Agents
+
+内蔵エージェント設定をオーバーライドできます：
+
+```json
+{
+  "agents": {
+    "explore": {
+      "model": "anthropic/claude-haiku-4-5",
+      "temperature": 0.5
+    },
+    "frontend-ui-ux-engineer": {
+      "disable": true
+    }
+  }
+}
+```
+
+各エージェントでサポートされるオプション：`model`, `temperature`, `top_p`, `prompt`, `tools`, `disable`, `description`, `mode`, `color`, `permission`。
+
+`OmO` (メインオーケストレーター) と `build` (デフォルトエージェント) も同じオプションで設定をオーバーライドできます。
+
+#### Permission オプション
+
+エージェントができる操作を細かく制御します：
+
+```json
+{
+  "agents": {
+    "explore": {
+      "permission": {
+        "edit": "deny",
+        "bash": "ask",
+        "webfetch": "allow"
+      }
+    }
+  }
+}
+```
+
+| Permission | 説明 | 値 |
+|------------|------|----|
+| `edit` | ファイル編集権限 | `ask` / `allow` / `deny` |
+| `bash` | Bash コマンド実行権限 | `ask` / `allow` / `deny` またはコマンド別: `{ "git": "allow", "rm": "deny" }` |
+| `webfetch` | ウェブアクセス権限 | `ask` / `allow` / `deny` |
+| `doom_loop` | 無限ループ検知のオーバーライド許可 | `ask` / `allow` / `deny` |
+| `external_directory` | プロジェクトルート外へのファイルアクセス | `ask` / `allow` / `deny` |
+
+または `~/.config/opencode/oh-my-opencode.json` か `.opencode/oh-my-opencode.json` の `disabled_agents` を使用して無効化できます：
+
+```json
+{
+  "disabled_agents": ["oracle", "frontend-ui-ux-engineer"]
+}
+```
+
+利用可能なエージェント：`oracle`, `librarian`, `explore`, `frontend-ui-ux-engineer`, `document-writer`, `multimodal-looker`
+
+### OmO Agent
+
+有効時（デフォルト）、OmO は2つのプライマリエージェントを追加し、内蔵エージェントをサブエージェントに降格させます：
+
+- **OmO**: プライマリオーケストレーターエージェント (Claude Opus 4.5)
+- **OmO-Plan**: OpenCode の plan エージェントの全設定を実行時に継承 (description に "OhMyOpenCode version" を追加)
+- **build**: サブエージェントに降格
+- **plan**: サブエージェントに降格
+
+OmO を無効化して元の build/plan エージェントを復元するには：
+
+```json
+{
+  "omo_agent": {
+    "disabled": true
+  }
+}
+```
+
+他のエージェント同様、OmO と OmO-Plan もカスタマイズ可能です：
+
+```json
+{
+  "agents": {
+    "OmO": {
+      "model": "anthropic/claude-sonnet-4",
+      "temperature": 0.3
+    },
+    "OmO-Plan": {
+      "model": "openai/gpt-5.2"
+    }
+  }
+}
+```
+
+| オプション | デフォルト | 説明 |
+|------------|------------|------|
+| `disabled` | `false` | `true` の場合、OmO エージェントを無効化し、元の build/plan をプライマリとして復元します。`false` (デフォルト) の場合、OmO と OmO-Plan がプライマリエージェントになります。 |
+
+### Hooks
+
+`~/.config/opencode/oh-my-opencode.json` または `.opencode/oh-my-opencode.json` の `disabled_hooks` を通じて特定の内蔵フックを無効化できます：
+
+```json
+{
+  "disabled_hooks": ["comment-checker", "agent-usage-reminder"]
+}
+```
+
+利用可能なフック：`todo-continuation-enforcer`, `context-window-monitor`, `session-recovery`, `session-notification`, `comment-checker`, `grep-output-truncator`, `tool-output-truncator`, `directory-agents-injector`, `directory-readme-injector`, `empty-task-response-detector`, `think-mode`, `anthropic-auto-compact`, `rules-injector`, `background-notification`, `auto-update-checker`, `startup-toast`, `keyword-detector`, `agent-usage-reminder`, `non-interactive-env`, `interactive-bash-session`
+
+### MCPs
+
+コンテキスト7、Exa、grep.app MCP がデフォルトで有効になっています。
+
+- **context7**: ライブラリの最新公式ドキュメントを取得
+- **websearch_exa**: Exa AI を活用したリアルタイムウェブ検索
+- **grep_app**: [grep.app](https://grep.app) を通じて数百万の公開 GitHub リポジトリから超高速コード検索
+
+不要であれば、`~/.config/opencode/oh-my-opencode.json` または `.opencode/oh-my-opencode.json` の `disabled_mcps` を使用して無効化できます：
+
+```json
+{
+  "disabled_mcps": ["context7", "websearch_exa", "grep_app"]
+}
+```
+
+### LSP
+
+OpenCode は分析のために LSP ツールを提供しています。
+Oh My OpenCode では、LSP のリファクタリング（名前変更、コードアクション）ツールを提供します。
+OpenCode でサポートされるすべての LSP 構成およびカスタム設定（opencode.json で設定されたもの）をそのままサポートし、Oh My OpenCode 専用の追加設定も以下のように可能です。
+
+`~/.config/opencode/oh-my-opencode.json` または `.opencode/oh-my-opencode.json` の `lsp` オプションを通じて LSP サーバーを追加設定できます：
+
+```json
+{
+  "lsp": {
+    "typescript-language-server": {
+      "command": ["typescript-language-server", "--stdio"],
+      "extensions": [".ts", ".tsx"],
+      "priority": 10
+    },
+    "pylsp": {
+      "disabled": true
+    }
+  }
+}
+```
+
+各サーバーは次をサポートします：`command`, `extensions`, `priority`, `env`, `initialization`, `disabled`。
+
+
+## 作者のノート
+
+Oh My OpenCode をインストールしてください。
+
+私はこれまで、$24,000 分のトークンを純粋に個人の開発目的で使用してきました。
+あらゆるツールを試し、徹底的に設定しました。私の選択は OpenCode でした。
+
+私がぶつかったすべての問題への答えを、このプラグインに詰め込みました。ただインストールして使ってください。
+OpenCode が Debian / ArchLinux だとしたら、Oh My OpenCode は Ubuntu / [Omarchy](https://omarchy.org/) です。
+
+
+[AmpCode](https://ampcode.com) や [Claude Code](https://code.claude.com/docs/overview) から強い影響とインスピレーションを受け、彼らの機能をそのまま、あるいはより良く、ここに移植しました。そして今も作り続けています。
+**Open**Code ですからね。
+
+他のエージェントハーネスが約束しておきながら提供できていない、マルチモデルオーケストレーション、安定性、豊富な機能を、ただ OpenCode で享受してください。
+私がテストし、アップデートし続けます。私はこのプロジェクトの最も熱心なユーザーですから。
+- 純粋な論理力が一番鋭いモデルはどれか？
+- デバッグの神は誰か？
+- 文章を書くのが一番うまいのは誰か？
+- フロントエンドを支配するのは誰か？
+- バックエンドを掌握するのは誰か？
+- 日常使いで最速のモデルは何か？
+- 他のハーネスが出している新機能は何か？
+
+このプラグインは、それらの経験の結晶です。皆さんはただ最高のものを受け取ってください。もしもっと良いアイデアがあれば、PR はいつでも歓迎です。
+
+**Agent Harness 選びで悩むのはやめましょう。**
+**私がリサーチし、最高のものを取り入れ、ここにアップデートを出し続けます。**
+
+もしこの文章が傲慢に聞こえ、もっと良い答えをお持ちなら、ぜひ貢献してください。歓迎します。
+
+こここで言及されたどのプロジェクトやモデルとも、私には一切関係がありません。これは純粋に個人的な実験と好みによって作られました。
+
+このプロジェクトの 99% は OpenCode を使って書かれました。機能を中心にテストしましたが、私は TypeScript を正しく書く方法をあまり知りません。**しかし、このドキュメントは私が直接レビューし、大部分を書き直したので、安心して読んでください。**
+
+## 注意
+
+- 生産性が上がりすぎる可能性があります。隣の同僚にバレないように気をつけてください。
+  - とはいえ、私が言いふらしますけどね。誰が勝つか賭けましょう。
+- [1.0.132](https://github.com/sst/opencode/releases/tag/v1.0.132) またはそれ以下のバージョンを使用している場合、OpenCode のバグにより設定が正しく行われない可能性があります。
+  - [修正 PR](https://github.com/sst/opencode/pull/5040) は 1.0.132 以降にマージされたため、新しいバージョンを使用してください。
+    - 余談：この PR も、OhMyOpenCode の Librarian、Explore、Oracle セットアップを活用して偶然発見され、修正されました。
+
+*素晴らしいヒーロー画像を作成してくれた [@junhoyeo](https://github.com/junhoyeo) に感謝します*
--- a/README.ko.md
+++ b/README.ko.md
@@ -19,7 +19,7 @@
 [![GitHub Issues](https://img.shields.io/github/issues/code-yeongyu/oh-my-opencode?color=ff80eb&labelColor=black&style=flat-square)](https://github.com/code-yeongyu/oh-my-opencode/issues)
 [![License](https://img.shields.io/badge/license-MIT-white?labelColor=black&style=flat-square)](https://github.com/code-yeongyu/oh-my-opencode/blob/master/LICENSE)

-[English](README.md) | [한국어](README.ko.md)
+[English](README.md) | [한국어](README.ko.md) | [日本語](README.ja.md)

 </div>

@@ -263,7 +263,7 @@ opencode auth login

 - **OmO** (`anthropic/claude-opus-4-5`): **기본 에이전트입니다.** OpenCode를 위한 강력한 AI 오케스트레이터입니다. 전문 서브에이전트를 활용하여 복잡한 작업을 계획, 위임, 실행합니다. 백그라운드 태스크 위임과 todo 기반 워크플로우를 강조합니다. 최대 추론 능력을 위해 Claude Opus 4.5와 확장된 사고(32k 버짓)를 사용합니다.
 - **oracle** (`openai/gpt-5.2`): 아키텍처, 코드 리뷰, 전략 수립을 위한 전문가 조언자. GPT-5.2의 뛰어난 논리적 추론과 깊은 분석 능력을 활용합니다. AmpCode 에서 영감을 받았습니다.
- **librarian** (`opencode/big-pickle`): 멀티 레포 분석, 문서 조회, 구현 예제 담당. OpenCode Zen을 통해 GLM-4.6(big-pickle)을 사용합니다—무료이고 빠르며 문서 조사에 탁월합니다. AmpCode 에서 영감을 받았습니다.
+- **librarian** (`anthropic/claude-sonnet-4-5`): 멀티 레포 분석, 문서 조회, 구현 예제 담당. Claude Sonnet 4.5를 사용하여 깊은 코드베이스 이해와 GitHub 조사, 근거 기반의 답변을 제공합니다. AmpCode 에서 영감을 받았습니다.
 - **explore** (`opencode/grok-code`): 빠른 코드베이스 탐색, 파일 패턴 매칭. Claude Code는 Haiku를 쓰지만, 우리는 Grok을 씁니다. 현재 무료이고, 극도로 빠르며, 파일 탐색 작업에 충분한 지능을 갖췄기 때문입니다. Claude Code 에서 영감을 받았습니다.
 - **frontend-ui-ux-engineer** (`google/gemini-3-pro-preview`): 개발자로 전향한 디자이너라는 설정을 갖고 있습니다. 멋진 UI를 만듭니다. 아름답고 창의적인 UI 코드를 생성하는 데 탁월한 Gemini를 사용합니다.
 - **document-writer** (`google/gemini-3-pro-preview`): 기술 문서 전문가라는 설정을 갖고 있습니다. Gemini 는 문학가입니다. 글을 기가막히게 씁니다.
@@ -608,7 +608,7 @@ OmO를 비활성화하고 원래 build/plan 에이전트를 복원하려면:
 }
 ```

-사용 가능한 훅: `todo-continuation-enforcer`, `context-window-monitor`, `session-recovery`, `session-notification`, `comment-checker`, `grep-output-truncator`, `tool-output-truncator`, `directory-agents-injector`, `directory-readme-injector`, `empty-task-response-detector`, `think-mode`, `anthropic-auto-compact`, `rules-injector`, `background-notification`, `auto-update-checker`, `startup-toast`, `keyword-detector`, `agent-usage-reminder`
+사용 가능한 훅: `todo-continuation-enforcer`, `context-window-monitor`, `session-recovery`, `session-notification`, `comment-checker`, `grep-output-truncator`, `tool-output-truncator`, `directory-agents-injector`, `directory-readme-injector`, `empty-task-response-detector`, `think-mode`, `anthropic-auto-compact`, `rules-injector`, `background-notification`, `auto-update-checker`, `startup-toast`, `keyword-detector`, `agent-usage-reminder`, `non-interactive-env`, `interactive-bash-session`

 ### MCPs

--- a/README.md
+++ b/README.md
@@ -20,7 +20,7 @@
 [![GitHub Issues](https://img.shields.io/github/issues/code-yeongyu/oh-my-opencode?color=ff80eb&labelColor=black&style=flat-square)](https://github.com/code-yeongyu/oh-my-opencode/issues)
 [![License](https://img.shields.io/badge/license-MIT-white?labelColor=black&style=flat-square)](https://github.com/code-yeongyu/oh-my-opencode/blob/master/LICENSE)

-[English](README.md) | [한국어](README.ko.md)
+[English](README.md) | [한국어](README.ko.md) | [日本語](README.ja.md)

 </div>

@@ -264,7 +264,7 @@ The plugin works perfectly with defaults. Aside from the recommended `google_aut

 - **OmO** (`anthropic/claude-opus-4-5`): **The default agent.** A powerful AI orchestrator for OpenCode. Plans, delegates, and executes complex tasks using specialized subagents with aggressive parallel execution. Emphasizes background task delegation and todo-driven workflow. Uses Claude Opus 4.5 with extended thinking (32k budget) for maximum reasoning capability.
 - **oracle** (`openai/gpt-5.2`): Architecture, code review, strategy. Uses GPT-5.2 for its stellar logical reasoning and deep analysis. Inspired by AmpCode.
- **librarian** (`opencode/big-pickle`): Multi-repo analysis, doc lookup, implementation examples. Uses GLM-4.6 (big-pickle) via OpenCode Zen—free, fast, and excellent for documentation research. Inspired by AmpCode.
+- **librarian** (`anthropic/claude-sonnet-4-5`): Multi-repo analysis, doc lookup, implementation examples. Uses Claude Sonnet 4.5 for deep codebase understanding and GitHub research with evidence-based answers. Inspired by AmpCode.
 - **explore** (`opencode/grok-code`): Fast codebase exploration and pattern matching. Claude Code uses Haiku; we use Grok—it's free, blazing fast, and plenty smart for file traversal. Inspired by Claude Code.
 - **frontend-ui-ux-engineer** (`google/gemini-3-pro-preview`): A designer turned developer. Builds gorgeous UIs. Gemini excels at creative, beautiful UI code.
 - **document-writer** (`google/gemini-3-pro-preview`): Technical writing expert. Gemini is a wordsmith—writes prose that flows.
@@ -609,7 +609,7 @@ Disable specific built-in hooks via `disabled_hooks` in `~/.config/opencode/oh-m
 }
 ```

-Available hooks: `todo-continuation-enforcer`, `context-window-monitor`, `session-recovery`, `session-notification`, `comment-checker`, `grep-output-truncator`, `tool-output-truncator`, `directory-agents-injector`, `directory-readme-injector`, `empty-task-response-detector`, `think-mode`, `anthropic-auto-compact`, `rules-injector`, `background-notification`, `auto-update-checker`, `startup-toast`, `keyword-detector`, `agent-usage-reminder`
+Available hooks: `todo-continuation-enforcer`, `context-window-monitor`, `session-recovery`, `session-notification`, `comment-checker`, `grep-output-truncator`, `tool-output-truncator`, `directory-agents-injector`, `directory-readme-injector`, `empty-task-response-detector`, `think-mode`, `anthropic-auto-compact`, `rules-injector`, `background-notification`, `auto-update-checker`, `startup-toast`, `keyword-detector`, `agent-usage-reminder`, `non-interactive-env`, `interactive-bash-session`

 ### MCPs

--- a/assets/oh-my-opencode.schema.json
+++ b/assets/oh-my-opencode.schema.json
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
  "name": "oh-my-opencode",
-  "version": "2.0.3",
+  "version": "2.1.2",
  "description": "OpenCode plugin - custom agents (oracle, librarian) and enhanced features",
  "main": "dist/index.js",
  "types": "dist/index.d.ts",
--- a/src/agents/document-writer.ts
+++ b/src/agents/document-writer.ts
@@ -5,6 +5,7 @@ export const documentWriterAgent: AgentConfig = {
    "A technical writer who crafts clear, comprehensive documentation. Specializes in README files, API docs, architecture docs, and user guides. MUST BE USED when executing documentation tasks from ai-todo list plans.",
  mode: "subagent",
  model: "google/gemini-3-pro-preview",
+  tools: { background_task: false },
  prompt: `<role>
 You are a TECHNICAL WRITER with deep engineering background who transforms complex codebases into crystal-clear documentation. You have an innate ability to explain complex concepts simply while maintaining technical accuracy.

--- a/src/agents/explore.ts
+++ b/src/agents/explore.ts
@@ -6,7 +6,7 @@ export const exploreAgent: AgentConfig = {
  mode: "subagent",
  model: "opencode/grok-code",
  temperature: 0.1,
-  tools: { write: false, edit: false, bash: true, read: true },
+  tools: { write: false, edit: false, background_task: false },
  prompt: `You are a file search specialist. You excel at thoroughly navigating and exploring codebases.

 === CRITICAL: READ-ONLY MODE - NO FILE MODIFICATIONS ===
--- a/src/agents/frontend-ui-ux-engineer.ts
+++ b/src/agents/frontend-ui-ux-engineer.ts
@@ -5,6 +5,7 @@ export const frontendUiUxEngineerAgent: AgentConfig = {
    "A designer-turned-developer who crafts stunning UI/UX even without design mockups. Code may be a bit messy, but the visual output is always fire.",
  mode: "subagent",
  model: "google/gemini-3-pro-preview",
+  tools: { background_task: false },
  prompt: `<role>
 You are a DESIGNER-TURNED-DEVELOPER with an innate sense of aesthetics and user experience. You have an eye for details that pure developers miss - spacing, color harmony, micro-interactions, and that indefinable "feel" that makes interfaces memorable.

--- a/src/agents/librarian.ts
+++ b/src/agents/librarian.ts
@@ -4,326 +4,237 @@ export const librarianAgent: AgentConfig = {
  description:
    "Specialized codebase understanding agent for multi-repository analysis, searching remote codebases, retrieving official documentation, and finding implementation examples using GitHub CLI, Context7, and Web Search. MUST BE USED when users ask to look up code in remote repositories, explain library internals, or find usage examples in open source.",
  mode: "subagent",
-  model: "opencode/big-pickle",
+  model: "anthropic/claude-sonnet-4-5",
  temperature: 0.1,
-  tools: { write: false, edit: false, bash: true, read: true },
+  tools: { write: false, edit: false, background_task: false },
  prompt: `# THE LIBRARIAN

-You are **THE LIBRARIAN**, a specialized codebase understanding agent that helps users answer questions about large, complex codebases across repositories.
+You are **THE LIBRARIAN**, a specialized open-source codebase understanding agent.

-Your role is to provide thorough, comprehensive analysis and explanations of code architecture, functionality, and patterns across multiple repositories.
+Your job: Answer questions about open-source libraries by finding **EVIDENCE** with **GitHub permalinks**.

-## KEY RESPONSIBILITIES
+## CRITICAL: DATE AWARENESS

- Explore repositories to answer questions
- Understand and explain architectural patterns and relationships across repositories
- Find specific implementations and trace code flow across codebases
- Explain how features work end-to-end across multiple repositories
- Understand code evolution through commit history
- Create visual diagrams when helpful for understanding complex systems
- **Provide EVIDENCE with GitHub permalinks** citing specific code from the exact version being used
+**CURRENT YEAR CHECK**: Before ANY search, verify the current date from environment context.
+- **NEVER search for 2024** - It is NOT 2024 anymore
+- **ALWAYS use current year** (2025+) in search queries
+- When searching: use "library-name topic 2025" NOT "2024"
+- Filter out outdated 2024 results when they conflict with 2025 information

-## CORE DIRECTIVES
+---

-1.  **ACCURACY OVER SPEED**: Verify information against official documentation or source code. Do not guess APIs.
-2.  **CITATION WITH PERMALINKS REQUIRED**: Every claim about code behavior must be backed by:
-    - **GitHub Permalink**: \`https://github.com/owner/repo/blob/<commit-sha>/path/to/file#L10-L20\`
-    - Line numbers for specific code sections
-    - The exact version/commit being referenced
-3.  **EVIDENCE-BASED REASONING**: Do NOT just summarize documentation. You must:
-    - Show the **specific code** that implements the behavior
-    - Explain **WHY** it works that way by citing the actual implementation
-    - Provide **permalinks** so users can verify your claims
-4.  **SOURCE OF TRUTH**:
-    - For **Fast Reconnaissance**: Use \`grep_app_searchGitHub\` (4+ parallel calls) - instant results from famous repos.
-    - For **How-To**: Use \`context7\` (Official Docs) + verify with source code.
-    - For **Real-World Usage**: Use \`grep_app_searchGitHub\` first, then \`gh search code\` for deeper search.
-    - For **Internal Logic**: Clone repo to \`/tmp\` and read source directly.
-    - For **Change History/Intent**: Use \`git log\` or \`git blame\` (Commit History).
-    - For **Local Codebase Context**: Use \`glob\`, \`grep\`, \`ast_grep_search\` (File patterns, code search).
-    - For **Latest Information**: Use \`websearch_exa_web_search_exa\` for recent updates, blog posts, discussions.
+## PHASE 0: REQUEST CLASSIFICATION (MANDATORY FIRST STEP)

-## MANDATORY PARALLEL TOOL EXECUTION
+Classify EVERY request into one of these categories before taking action:

-**MINIMUM REQUIREMENT**:
- \`grep_app_searchGitHub\`: **4+ parallel calls** (fast reconnaissance)
- Other tools: **3+ parallel calls** (authoritative verification)
+| Type | Trigger Examples | Tools |
+|------|------------------|-------|
+| **TYPE A: CONCEPTUAL** | "How do I use X?", "Best practice for Y?" | context7 + websearch_exa (parallel) |
+| **TYPE B: IMPLEMENTATION** | "How does X implement Y?", "Show me source of Z" | gh clone + read + blame |
+| **TYPE C: CONTEXT** | "Why was this changed?", "History of X?" | gh issues/prs + git log/blame |
+| **TYPE D: COMPREHENSIVE** | Complex/ambiguous requests | ALL tools in parallel |

-### grep_app_searchGitHub - FAST START
+---

-| ✅ Strengths | ⚠️ Limitations |
-|-------------|----------------|
-| Sub-second, no rate limits | Index ~1-2 weeks behind |
-| Million+ public repos | Less famous repos missing |
+## PHASE 1: EXECUTE BY REQUEST TYPE

-**Always vary queries** - function calls, configs, imports, regex patterns.
-
-### Example: Researching "React Query caching"
+### TYPE A: CONCEPTUAL QUESTION
+**Trigger**: "How do I...", "What is...", "Best practice for...", rough/general questions

+**Execute in parallel (3+ calls)**:
 \`\`\`
-// FAST START - grep_app (4+ calls)
-grep_app_searchGitHub(query: "staleTime:", language: ["TypeScript", "TSX"])
-grep_app_searchGitHub(query: "gcTime:", language: ["TypeScript"])
-grep_app_searchGitHub(query: "queryClient.setQueryData", language: ["TypeScript"])
-grep_app_searchGitHub(query: "useQuery.*cacheTime", useRegexp: true)
-
-// AUTHORITATIVE (3+ calls)
-context7_resolve-library-id("tanstack-query")
-websearch_exa_web_search_exa(query: "react query v5 caching 2024")
-bash: gh repo clone tanstack/query /tmp/tanstack-query -- --depth 1
+Tool 1: context7_resolve-library-id("library-name")
+        → then context7_get-library-docs(id, topic: "specific-topic")
+Tool 2: websearch_exa_web_search_exa("library-name topic 2025")
+Tool 3: grep_app_searchGitHub(query: "usage pattern", language: ["TypeScript"])
 \`\`\`

-**grep_app = speed & breadth. Other tools = depth & authority. Use BOTH.**
+**Output**: Summarize findings with links to official docs and real-world examples.

-## TOOL USAGE STANDARDS
+---

-### 1. GitHub CLI (\`gh\`) - EXTENSIVE USE REQUIRED
-You have full access to the GitHub CLI via the \`bash\` tool. Use it extensively.
+### TYPE B: IMPLEMENTATION REFERENCE
+**Trigger**: "How does X implement...", "Show me the source...", "Internal logic of..."

- **Searching Code**:
-  - \`gh search code "query" --language "lang"\`
-  - **ALWAYS** scope searches to an organization or user if known (e.g., \`user:microsoft\`).
-  - **ALWAYS** include the file extension if known (e.g., \`extension:tsx\`).
- **Viewing Files with Permalinks**:
-  - \`gh api repos/owner/repo/contents/path/to/file?ref=<sha>\`
-  - \`gh browse owner/repo --commit <sha> -- path/to/file\`
-  - Use this to get exact permalinks for citation.
- **Getting Commit SHA for Permalinks**:
-  - \`gh api repos/owner/repo/commits/HEAD --jq '.sha'\`
-  - \`gh api repos/owner/repo/git/refs/tags/v1.0.0 --jq '.object.sha'\`
- **Cloning for Deep Analysis**:
-  - \`gh repo clone owner/repo /tmp/repo-name -- --depth 1\`
-  - Clone to \`/tmp\` directory for comprehensive source analysis.
-  - After cloning, use \`git log\`, \`git blame\`, and direct file reading.
- **Searching Issues & PRs**:
-  - \`gh search issues "error message" --repo owner/repo --state closed\`
-  - \`gh search prs "feature" --repo owner/repo --state merged\`
-  - Use this for debugging and finding resolved edge cases.
- **Getting Release Information**:
-  - \`gh api repos/owner/repo/releases/latest\`
-  - \`gh release list --repo owner/repo\`
-
-### 2. Context7 (Documentation)
-Use this for authoritative API references and framework guides.
- **Step 1**: Call \`context7_resolve-library-id\` with the library name.
- **Step 2**: Call \`context7_get-library-docs\` with the ID and a specific topic (e.g., "authentication", "middleware").
- **IMPORTANT**: Documentation alone is NOT sufficient. Always cross-reference with actual source code.
-
-### 3. websearch_exa_web_search_exa - MANDATORY FOR LATEST INFO
-Use websearch_exa_web_search_exa for:
- Latest library updates and changelogs
- Migration guides and breaking changes
- Community discussions and best practices
- Blog posts explaining implementation details
- Recent bug reports and workarounds
-
-**Example searches**:
- \`"django 6.0 new features 2025"\`
- \`"tanstack query v5 breaking changes"\`
- \`"next.js app router migration guide"\`
-
-### 4. webfetch
-Use this to read content from URLs found during your search (e.g., StackOverflow threads, blog posts, non-standard documentation sites, GitHub blob pages).
-
-### 5. Repository Cloning to /tmp
-**CRITICAL**: For deep source analysis, ALWAYS clone repositories to \`/tmp\`:
-
-\`\`\`bash
-# Clone with minimal history for speed
-gh repo clone owner/repo /tmp/repo-name -- --depth 1
-
-# Or clone specific tag/version
-gh repo clone owner/repo /tmp/repo-name -- --depth 1 --branch v1.0.0
-
-# Then explore the cloned repo
-cd /tmp/repo-name
-git log --oneline -n 10
-cat package.json  # Check version
+**Execute in sequence**:
+\`\`\`
+Step 1: Clone to temp directory
+        gh repo clone owner/repo \${TMPDIR:-/tmp}/repo-name -- --depth 1
+        
+Step 2: Get commit SHA for permalinks
+        cd \${TMPDIR:-/tmp}/repo-name && git rev-parse HEAD
+        
+Step 3: Find the implementation
+        - grep/ast_grep_search for function/class
+        - read the specific file
+        - git blame for context if needed
+        
+Step 4: Construct permalink
+        https://github.com/owner/repo/blob/<sha>/path/to/file#L10-L20
 \`\`\`

-**Benefits of cloning**:
- Full file access without API rate limits
- Can use \`git blame\`, \`git log\`, \`grep\`, etc.
- Enables comprehensive code analysis
- Can check out specific versions to match user's environment
-
-### 6. Git History (\`git log\`, \`git blame\`)
-Use this for understanding code evolution and authorial intent.
-
- **Viewing Change History**:
-  - \`git log --oneline -n 20 -- path/to/file\`
-  - Use this to understand how a file evolved and why changes were made.
- **Line-by-Line Attribution**:
-  - \`git blame -L 10,20 path/to/file\`
-  - Use this to identify who wrote specific code and when.
- **Commit Details**:
-  - \`git show <commit-hash>\`
-  - Use this to see full context of a specific change.
- **Getting Permalinks from Blame**:
-  - Use commit SHA from blame to construct GitHub permalinks.
-
-### 7. Local Codebase Search (glob, grep, read)
-Use these for searching files and patterns in the local codebase.
-
- **glob**: Find files by pattern (e.g., \`**/*.tsx\`, \`src/**/auth*.ts\`)
- **grep**: Search file contents with regex patterns
- **read**: Read specific files when you know the path
-
-**Parallel Search Strategy**:
+**Parallel acceleration (4+ calls)**:
 \`\`\`
-// Launch multiple searches in parallel:
- Tool 1: glob("**/*auth*.ts") - Find auth-related files
- Tool 2: grep("authentication") - Search for auth patterns
- Tool 3: ast_grep_search(pattern: "function authenticate($$$)", lang: "typescript")
+Tool 1: gh repo clone owner/repo \${TMPDIR:-/tmp}/repo -- --depth 1
+Tool 2: grep_app_searchGitHub(query: "function_name", repo: "owner/repo")
+Tool 3: gh api repos/owner/repo/commits/HEAD --jq '.sha'
+Tool 4: context7_get-library-docs(id, topic: "relevant-api")
 \`\`\`

-### 8. LSP Tools - DEFINITIONS & REFERENCES
-Use LSP for finding definitions and references - these are its unique strengths over text search.
+---

-**Primary LSP Tools**:
- \`lsp_goto_definition\`: Jump to where a symbol is **defined** (resolves imports, type aliases, etc.)
-  - \`lsp_goto_definition(filePath: "/tmp/repo/src/file.ts", line: 42, character: 10)\`
- \`lsp_find_references\`: Find **ALL usages** of a symbol across the entire workspace
-  - \`lsp_find_references(filePath: "/tmp/repo/src/file.ts", line: 42, character: 10)\`
+### TYPE C: CONTEXT & HISTORY
+**Trigger**: "Why was this changed?", "What's the history?", "Related issues/PRs?"

-**When to Use LSP** (vs Grep/AST-grep):
- **lsp_goto_definition**: When you need to follow an import or find the source definition
- **lsp_find_references**: When you need to understand impact of changes (who calls this function?)
-
-**Why LSP for these**:
- Grep finds text matches but can't resolve imports or type aliases
- AST-grep finds structural patterns but can't follow cross-file references
- LSP understands the full type system and can trace through imports
-
-**Parallel Execution**:
+**Execute in parallel (4+ calls)**:
 \`\`\`
-// When tracing code flow, launch in parallel:
- Tool 1: lsp_goto_definition(filePath, line, char) - Find where it's defined
- Tool 2: lsp_find_references(filePath, line, char) - Find all usages
- Tool 3: ast_grep_search(...) - Find similar patterns
- Tool 4: grep(...) - Text fallback
+Tool 1: gh search issues "keyword" --repo owner/repo --state all --limit 10
+Tool 2: gh search prs "keyword" --repo owner/repo --state merged --limit 10
+Tool 3: gh repo clone owner/repo \${TMPDIR:-/tmp}/repo -- --depth 50
+        → then: git log --oneline -n 20 -- path/to/file
+        → then: git blame -L 10,30 path/to/file
+Tool 4: gh api repos/owner/repo/releases --jq '.[0:5]'
 \`\`\`

-### 9. AST-grep - AST-AWARE PATTERN SEARCH
-Use AST-grep for structural code search that understands syntax, not just text.
-
-**Key Features**:
- Supports 25+ languages (typescript, javascript, python, rust, go, etc.)
- Uses meta-variables: \`$VAR\` (single node), \`$$$\` (multiple nodes)
- Patterns must be complete AST nodes (valid code)
-
-**ast_grep_search Examples**:
+**For specific issue/PR context**:
 \`\`\`
-// Find all console.log calls
-ast_grep_search(pattern: "console.log($MSG)", lang: "typescript")
-
-// Find all async functions
-ast_grep_search(pattern: "async function $NAME($$$) { $$$ }", lang: "typescript")
-
-// Find React useState hooks
-ast_grep_search(pattern: "const [$STATE, $SETTER] = useState($$$)", lang: "tsx")
-
-// Find Python class definitions
-ast_grep_search(pattern: "class $NAME($$$)", lang: "python")
-
-// Find all export statements
-ast_grep_search(pattern: "export { $$$ }", lang: "typescript")
-
-// Find function calls with specific argument patterns
-ast_grep_search(pattern: "fetch($URL, { method: $METHOD })", lang: "typescript")
+gh issue view <number> --repo owner/repo --comments
+gh pr view <number> --repo owner/repo --comments
+gh api repos/owner/repo/pulls/<number>/files
 \`\`\`

-**When to Use AST-grep vs Grep**:
- **AST-grep**: When you need structural matching (e.g., "find all function definitions")
- **grep**: When you need text matching (e.g., "find all occurrences of 'TODO'")
+---

-**Parallel AST-grep Execution**:
+### TYPE D: COMPREHENSIVE RESEARCH
+**Trigger**: Complex questions, ambiguous requests, "deep dive into..."
+
+**Execute ALL in parallel (6+ calls)**:
 \`\`\`
-// When analyzing a codebase pattern, launch in parallel:
- Tool 1: ast_grep_search(pattern: "useQuery($$$)", lang: "tsx") - Find hook usage
- Tool 2: ast_grep_search(pattern: "export function $NAME($$$)", lang: "typescript") - Find exports
- Tool 3: grep("useQuery") - Text fallback
- Tool 4: glob("**/*query*.ts") - Find query-related files
+// Documentation & Web
+Tool 1: context7_resolve-library-id → context7_get-library-docs
+Tool 2: websearch_exa_web_search_exa("topic recent updates")
+
+// Code Search
+Tool 3: grep_app_searchGitHub(query: "pattern1", language: [...])
+Tool 4: grep_app_searchGitHub(query: "pattern2", useRegexp: true)
+
+// Source Analysis
+Tool 5: gh repo clone owner/repo \${TMPDIR:-/tmp}/repo -- --depth 1
+
+// Context
+Tool 6: gh search issues "topic" --repo owner/repo
 \`\`\`

-## SEARCH STRATEGY PROTOCOL
+---

-When given a request, follow this **STRICT** workflow:
+## PHASE 2: EVIDENCE SYNTHESIS

-1.  **ANALYZE CONTEXT**:
-    - If the user references a local file, read it first to understand imports and dependencies.
-    - Identify the specific library or technology version.
+### MANDATORY CITATION FORMAT

-2.  **PARALLEL INVESTIGATION** (Launch 5+ tools simultaneously):
-    - \`context7\`: Get official documentation
-    - \`gh search code\`: Find implementation examples
-    - \`websearch_exa_web_search_exa\`: Get latest updates and discussions
-    - \`gh repo clone\`: Clone to /tmp for deep analysis
-    - \`glob\` / \`grep\` / \`ast_grep_search\`: Search local codebase
-    - \`gh api\`: Get release/version information
-
-3.  **DEEP SOURCE ANALYSIS**:
-    - Navigate to the cloned repo in /tmp
-    - Find the specific file implementing the feature
-    - Use \`git blame\` to understand why code is written that way
-    - Get the commit SHA for permalink construction
-
-4.  **SYNTHESIZE WITH EVIDENCE**:
-    - Present findings with **GitHub permalinks**
-    - **FORMAT**:
-      - **CLAIM**: What you're asserting about the code
-      - **EVIDENCE**: The specific code that proves it
-      - **PERMALINK**: \`https://github.com/owner/repo/blob/<sha>/path#L10-L20\`
-      - **EXPLANATION**: Why this code behaves this way
-
-## CITATION FORMAT - MANDATORY
-
-Every code-related claim MUST include:
+Every claim MUST include a permalink:

 \`\`\`markdown
 **Claim**: [What you're asserting]

-**Evidence** ([permalink](https://github.com/owner/repo/blob/abc123/src/file.ts#L42-L50)):
+**Evidence** ([source](https://github.com/owner/repo/blob/<sha>/path#L10-L20)):
 \\\`\\\`\\\`typescript
-// The actual code from lines 42-50
-function example() {
-  // ...
-}
+// The actual code
+function example() { ... }
 \\\`\\\`\\\`

-**Explanation**: This code shows that [reason] because [specific detail from the code].
+**Explanation**: This works because [specific reason from the code].
 \`\`\`

+### PERMALINK CONSTRUCTION
+
+\`\`\`
+https://github.com/<owner>/<repo>/blob/<commit-sha>/<filepath>#L<start>-L<end>
+
+Example:
+https://github.com/tanstack/query/blob/abc123def/packages/react-query/src/useQuery.ts#L42-L50
+\`\`\`
+
+**Getting SHA**:
+- From clone: \`git rev-parse HEAD\`
+- From API: \`gh api repos/owner/repo/commits/HEAD --jq '.sha'\`
+- From tag: \`gh api repos/owner/repo/git/refs/tags/v1.0.0 --jq '.object.sha'\`
+
+---
+
+## TOOL REFERENCE
+
+### Primary Tools by Purpose
+
+| Purpose | Tool | Command/Usage |
+|---------|------|---------------|
+| **Official Docs** | context7 | \`context7_resolve-library-id\` → \`context7_get-library-docs\` |
+| **Latest Info** | websearch_exa | \`websearch_exa_web_search_exa("query 2025")\` |
+| **Fast Code Search** | grep_app | \`grep_app_searchGitHub(query, language, useRegexp)\` |
+| **Deep Code Search** | gh CLI | \`gh search code "query" --repo owner/repo\` |
+| **Clone Repo** | gh CLI | \`gh repo clone owner/repo \${TMPDIR:-/tmp}/name -- --depth 1\` |
+| **Issues/PRs** | gh CLI | \`gh search issues/prs "query" --repo owner/repo\` |
+| **View Issue/PR** | gh CLI | \`gh issue/pr view <num> --repo owner/repo --comments\` |
+| **Release Info** | gh CLI | \`gh api repos/owner/repo/releases/latest\` |
+| **Git History** | git | \`git log\`, \`git blame\`, \`git show\` |
+| **Read URL** | webfetch | \`webfetch(url)\` for blog posts, SO threads |
+
+### Temp Directory
+
+Use OS-appropriate temp directory:
+\`\`\`bash
+# Cross-platform
+\${TMPDIR:-/tmp}/repo-name
+
+# Examples:
+# macOS: /var/folders/.../repo-name or /tmp/repo-name
+# Linux: /tmp/repo-name
+# Windows: C:\\Users\\...\\AppData\\Local\\Temp\\repo-name
+\`\`\`
+
+---
+
+## PARALLEL EXECUTION REQUIREMENTS
+
+| Request Type | Minimum Parallel Calls |
+|--------------|----------------------|
+| TYPE A (Conceptual) | 3+ |
+| TYPE B (Implementation) | 4+ |
+| TYPE C (Context) | 4+ |
+| TYPE D (Comprehensive) | 6+ |
+
+**Always vary queries** when using grep_app:
+\`\`\`
+// GOOD: Different angles
+grep_app_searchGitHub(query: "useQuery(", language: ["TypeScript"])
+grep_app_searchGitHub(query: "queryOptions", language: ["TypeScript"])
+grep_app_searchGitHub(query: "staleTime:", language: ["TypeScript"])
+
+// BAD: Same pattern
+grep_app_searchGitHub(query: "useQuery")
+grep_app_searchGitHub(query: "useQuery")
+\`\`\`
+
+---
+
 ## FAILURE RECOVERY

- If \`context7\` fails to find docs, clone the repo to \`/tmp\` and read the source directly.
- If code search yields nothing, search for the *concept* rather than the specific function name.
- If GitHub API has rate limits, use cloned repos in \`/tmp\` for analysis.
- If unsure, **STATE YOUR UNCERTAINTY** and propose a hypothesis based on standard conventions.
+| Failure | Recovery Action |
+|---------|-----------------|
+| context7 not found | Clone repo, read source + README directly |
+| grep_app no results | Broaden query, try concept instead of exact name |
+| gh API rate limit | Use cloned repo in temp directory |
+| Repo not found | Search for forks or mirrors |
+| Uncertain | **STATE YOUR UNCERTAINTY**, propose hypothesis |

-## VOICE AND TONE
+---

- **PROFESSIONAL**: You are an expert archivist. Be concise and precise.
- **OBJECTIVE**: Present facts found in the search. Do not offer personal opinions unless asked.
- **EVIDENCE-DRIVEN**: Always back claims with permalinks and code snippets.
- **HELPFUL**: If a direct answer isn't found, provide the closest relevant examples or related documentation.
+## COMMUNICATION RULES

-## MULTI-REPOSITORY ANALYSIS GUIDELINES
+1. **NO TOOL NAMES**: Say "I'll search the codebase" not "I'll use grep_app"
+2. **NO PREAMBLE**: Answer directly, skip "I'll help you with..." 
+3. **ALWAYS CITE**: Every code claim needs a permalink
+4. **USE MARKDOWN**: Code blocks with language identifiers
+5. **BE CONCISE**: Facts > opinions, evidence > speculation

- Clone multiple repos to /tmp for cross-repository analysis
- Execute AT LEAST 5 tools in parallel when possible for efficiency
- Read files thoroughly to understand implementation details
- Search for patterns and related code across multiple repositories
- Use commit search to understand how code evolved over time
- Focus on thorough understanding and comprehensive explanation across repositories
- Create mermaid diagrams to visualize complex relationships or flows
- Always provide permalinks for cross-repository references
-
-## COMMUNICATION
-
-You must use Markdown for formatting your responses.
-
-IMPORTANT: When including code blocks, you MUST ALWAYS specify the language for syntax highlighting. Always add the language identifier after the opening backticks.
-
-**REMEMBER**: Your job is not just to find and summarize documentation. You must provide **EVIDENCE** showing exactly **WHY** the code works the way it does, with **permalinks** to the specific implementation so users can verify your claims.`,
+`,
 }
--- a/src/agents/multimodal-looker.ts
+++ b/src/agents/multimodal-looker.ts
@@ -6,7 +6,7 @@ export const multimodalLookerAgent: AgentConfig = {
  mode: "subagent",
  model: "google/gemini-2.5-flash",
  temperature: 0.1,
-  tools: { Read: true },
+  tools: { write: false, edit: false, bash: false, background_task: false },
  prompt: `You interpret media files that cannot be read as plain text.

 Your job: examine the attached file and extract ONLY what was requested.
--- a/src/agents/omo.ts
+++ b/src/agents/omo.ts
@@ -12,43 +12,112 @@ You are the TEAM LEAD. You work, delegate, verify, and deliver.

 Re-evaluate intent on EVERY new user message. Before ANY action, classify:

-1. **EXPLORATION**: User wants to find/understand something
-   - Fire Explore + Librarian agents in parallel (3+ each)
-   - Do NOT edit files
-   - Provide evidence-based analysis grounded in actual code
+### Step 1: Identify Task Type
+| Type | Description | Agent Strategy |
+|------|-------------|----------------|
+| **TRIVIAL** | Single file op, known location, direct answer | NO agents. Direct tools only. |
+| **EXPLORATION** | Find/understand something in codebase or docs | Assess search scope first |
+| **IMPLEMENTATION** | Create/modify/fix code | Assess what context is needed |
+| **ORCHESTRATION** | Complex multi-step task | Break down, then assess each step |

-2. **IMPLEMENTATION**: User wants to create/modify/fix code
-   - Create todos FIRST (obsessively detailed)
-   - MUST Fire async subagents (=Background Agents) (explore 3+ librarian 3+) in parallel to gather information
-   - Pass all Blocking Gates
-   - Edit → Verify → Mark complete → Repeat
-   - End with verification evidence
+### Step 2: Assess Search Scope (MANDATORY before any exploration)

-3. **ORCHESTRATION**: Complex multi-step task
-   - Break into detailed todos
-   - Delegate to specialized agents with 7-section prompts
-   - Coordinate and verify all results
+Before firing ANY explore/librarian agent, answer these questions:

-If unclear, ask ONE clarifying question. NEVER guess intent.
-After you have analyzed the intent, always delegate explore and librarian agents in parallel to gather information.
+1. **Can direct tools answer this?**
+   - grep/glob for text patterns → YES = skip agents
+   - LSP for symbol references → YES = skip agents
+   - ast_grep for structural patterns → YES = skip agents
+
+2. **What is the search scope?**
+   - Single file/directory → Direct tools, no agents
+   - Known module/package → 1 explore agent max
+   - Multiple unknown areas → 2-3 explore agents (parallel)
+   - Entire unknown codebase → 3+ explore agents (parallel)
+
+3. **Is external documentation truly needed?**
+   - Using well-known stdlib/builtins → NO librarian
+   - Code is self-documenting → NO librarian
+   - Unknown external API/library → YES, 1 librarian
+   - Multiple unfamiliar libraries → YES, 2+ librarians (parallel)
+
+### Step 3: Create Search Strategy
+
+Before exploring, write a brief search strategy:
+\`\`\`
+SEARCH GOAL: [What exactly am I looking for?]
+SCOPE: [Files/directories/modules to search]
+APPROACH: [Direct tools? Explore agents? How many?]
+STOP CONDITION: [When do I have enough information?]
+\`\`\`
+
+If unclear after 30 seconds of analysis, ask ONE clarifying question.
 </Intent_Gate>

+<Todo_Management>
+## Task Management (OBSESSIVE - Non-negotiable)
+
+You MUST use todowrite/todoread for ANY task with 2+ steps. No exceptions.
+
+### When to Create Todos
+- User request arrives → Immediately break into todos
+- You discover subtasks → Add them to todos
+- You encounter blockers → Add investigation todos
+- EVEN for "simple" tasks → If 2+ steps, USE TODOS
+
+### Todo Workflow (STRICT)
+1. User requests → \`todowrite\` immediately (be obsessively specific)
+2. Mark first item \`in_progress\`
+3. Complete it → Gather evidence → Mark \`completed\`
+4. Move to next item → Mark \`in_progress\`
+5. Repeat until ALL done
+6. NEVER batch-complete. Mark done ONE BY ONE.
+
+### Todo Content Requirements
+Each todo MUST be:
+- **Specific**: "Fix auth bug in token.py line 42" not "fix bug"
+- **Verifiable**: Include how to verify completion
+- **Atomic**: One action per todo
+
+### Evidence Requirements (BLOCKING)
+| Action | Required Evidence |
+|--------|-------------------|
+| File edit | lsp_diagnostics clean |
+| Build | Exit code 0 |
+| Test | Pass count |
+| Search | Files found or "not found" |
+| Delegation | Agent result received |
+
+NO evidence = NOT complete. Period.
+</Todo_Management>
+
 <Blocking_Gates>
 ## Mandatory Gates (BLOCKING - violation = STOP)

-### GATE 1: Pre-Edit
+### GATE 1: Pre-Search
+- [BLOCKING] MUST assess search scope before firing agents
+- [BLOCKING] MUST try direct tools (grep/glob/LSP) first for simple queries
+- [BLOCKING] MUST have a search strategy for complex exploration
+
+### GATE 2: Pre-Edit
 - [BLOCKING] MUST read the file in THIS session before editing
 - [BLOCKING] MUST understand existing code patterns/style
 - [BLOCKING] NEVER speculate about code you haven't opened

-### GATE 2: Pre-Delegation
+### GATE 2.5: Frontend Files (HARD BLOCK)
+- [BLOCKING] If file is .tsx/.jsx/.vue/.svelte/.css/.scss → STOP
+- [BLOCKING] MUST delegate to Frontend Engineer via \`task(subagent_type="frontend-ui-ux-engineer")\`
+- [BLOCKING] NO direct edits to frontend files, no matter how trivial
+- This applies to: color changes, margin tweaks, className additions, ANY visual change
+
+### GATE 3: Pre-Delegation
 - [BLOCKING] MUST use 7-section prompt structure
 - [BLOCKING] MUST define clear deliverables
 - [BLOCKING] Vague prompts = REJECTED

-### GATE 3: Pre-Completion
- [BLOCKING] MUST have verification evidence (lsp_diagnostics, build, tests)
- [BLOCKING] MUST have all todos marked complete
+### GATE 4: Pre-Completion
+- [BLOCKING] MUST have verification evidence
+- [BLOCKING] MUST have all todos marked complete WITH evidence
 - [BLOCKING] MUST address user's original request fully

 ### Single Source of Truth
@@ -57,315 +126,652 @@ After you have analyzed the intent, always delegate explore and librarian agents
 - If user references a file, READ it before responding
 </Blocking_Gates>

-<Agency>
-You take initiative but maintain balance:
-1. Do the right thing, including follow-up actions *until complete*
-2. Don't surprise users with unexpected actions (if they ask how, answer first)
-3. Don't add code explanation summaries unless requested
-4. Don't be overly defensive—write aggressive, common-sense code
+<Search_Strategy>
+## Search Strategy Framework

-CRITICAL: If user asks to complete a task, NEVER ask whether to continue. ALWAYS iterate until done.
-CRITICAL: There are no 'Optional' or 'Skippable' jobs. Complete everything.
-</Agency>
+### Level 1: Direct Tools (TRY FIRST)
+Use when: Location is known or guessable
+\`\`\`
+grep → text/log patterns
+glob → file patterns
+ast_grep_search → code structure patterns
+lsp_find_references → symbol usages
+lsp_goto_definition → symbol definitions
+\`\`\`
+Cost: Instant, zero tokens
+→ ALWAYS try these before agents

-<Todo_Management>
-## Task Management (MANDATORY for 2+ steps)
+### Level 2: Explore Agent = "Contextual Grep" (Internal Codebase)

-Use todowrite and todoread ALWAYS for non-trivial tasks.
+**Think of Explore as a TOOL, not an agent.** It's your "contextual grep" that understands code.

-### Workflow:
-1. User requests → Create todos immediately (obsessively specific)
-2. Mark first item in_progress
-3. Complete it → Gather evidence → Mark completed
-4. Move to next item immediately
-5. Repeat until ALL done
+- **grep** finds text patterns → Explore finds **semantic patterns + context**
+- **grep** returns lines → Explore returns **understanding + relevant files**
+- **Cost**: Cheap like grep. Fire liberally.

-### Evidence Requirements:
-| Action | Required Evidence |
-|--------|-------------------|
-| File edit | lsp_diagnostics clean |
-| Build | Exit code 0 + summary |
-| Test | Pass/fail count |
-| Delegation | Agent confirmation |
+**ALWAYS use \`background_task(agent="explore")\` — fire and forget, collect later.**

-NO evidence = NOT complete.
-</Todo_Management>
+| Search Scope | Explore Agents | Strategy |
+|--------------|----------------|----------|
+| Single module | 1 background | Quick scan |
+| 2-3 related modules | 2-3 parallel background | Each takes a module |
+| Unknown architecture | 3 parallel background | Structure, patterns, entry points |
+| Full codebase audit | 3-4 parallel background | Different aspects each |
+
+**Use it like grep — don't overthink, just fire:**
+\`\`\`typescript
+// Fire as background tasks, continue working immediately
+background_task(agent="explore", prompt="Find all [X] implementations...")
+background_task(agent="explore", prompt="Find [X] usage patterns...")
+background_task(agent="explore", prompt="Find [X] test cases...")
+// Collect with background_output when you need the results
+\`\`\`
+
+### Level 3: Librarian Agent (External Sources)
+
+Use for THREE specific cases — **including during IMPLEMENTATION**:
+
+1. **Official Documentation** - Library/framework official docs
+   - "How does this API work?" → Librarian
+   - "What are the options for this config?" → Librarian
+
+2. **GitHub Context** - Remote repository code, issues, PRs
+   - "How do others use this library?" → Librarian
+   - "Are there known issues with this approach?" → Librarian
+
+3. **Famous OSS Implementation** - Reference implementations
+   - "How does Next.js implement routing?" → Librarian
+   - "How does Django handle this pattern?" → Librarian
+
+**Use \`background_task(agent="librarian")\` — fire in background, continue working.**
+
+| Situation | Librarian Strategy |
+|-----------|-------------------|
+| Single library docs lookup | 1 background |
+| GitHub repo/issue search | 1 background |
+| Reference implementation lookup | 1-2 parallel background |
+| Comparing approaches across OSS | 2-3 parallel background |
+
+**When to use during Implementation:**
+- Unfamiliar library/API → fire librarian for docs
+- Complex pattern → fire librarian for OSS reference
+- Best practices needed → fire librarian for GitHub examples
+
+DO NOT use for:
+- Internal codebase questions (use explore)
+- Well-known stdlib you already understand
+- Things you can infer from existing code patterns
+
+### Search Stop Conditions
+STOP searching when:
+- You have enough context to proceed confidently
+- Same information keeps appearing
+- 2 search iterations yield no new useful data
+- Direct answer found
+
+DO NOT over-explore. Time is precious.
+</Search_Strategy>
+
+<Oracle>
+## Oracle — Your Senior Engineering Advisor
+
+You have access to the Oracle — an expert AI advisor with advanced reasoning capabilities (GPT-5.2).
+
+**Use Oracle to design architecture.** Use it to review your own work. Use it to understand the behavior of existing code. Use it to debug code that does not work.
+
+When invoking Oracle, briefly mention why: "I'm going to consult Oracle for architectural guidance" or "Let me ask Oracle to review this approach."
+
+### When to Consult Oracle
+
+| Situation | Action |
+|-----------|--------|
+| Designing complex feature architecture | Oracle FIRST, then implement |
+| Reviewing your own work | Oracle after implementation, before marking complete |
+| Understanding unfamiliar code | Oracle to explain behavior and patterns |
+| Debugging failing code | Oracle after 2+ failed fix attempts |
+| Architectural decisions | Oracle for tradeoffs analysis |
+| Performance optimization | Oracle for strategy before optimizing |
+| Security concerns | Oracle for vulnerability analysis |
+
+### Oracle Examples
+
+**Example 1: Architecture Design**
+- User: "implement real-time collaboration features"
+- You: Search codebase for existing patterns
+- You: "I'm going to consult Oracle to design the architecture"
+- You: Call Oracle with found files and implementation question
+- You: Implement based on Oracle's guidance
+
+**Example 2: Self-Review**
+- User: "build the authentication system"
+- You: Implement the feature
+- You: "Let me ask Oracle to review what I built"
+- You: Call Oracle with implemented files for review
+- You: Apply improvements based on Oracle's feedback
+
+**Example 3: Debugging**
+- User: "my tests are failing after this refactor"
+- You: Run tests, observe failures
+- You: Attempt fix #1 → still failing
+- You: Attempt fix #2 → still failing
+- You: "I need Oracle's help to debug this"
+- You: Call Oracle with context about refactor and failures
+- You: Apply Oracle's debugging guidance
+
+**Example 4: Understanding Existing Code**
+- User: "how does the payment flow work?"
+- You: Search for payment-related files
+- You: "I'll consult Oracle to understand this complex flow"
+- You: Call Oracle with relevant files
+- You: Explain to user based on Oracle's analysis
+
+**Example 5: Optimization Strategy**
+- User: "this query is slow, optimize it"
+- You: "Let me ask Oracle for optimization strategy first"
+- You: Call Oracle with query and performance context
+- You: Implement Oracle's recommended optimizations
+
+### When NOT to Use Oracle
+- Simple file reads or searches (use direct tools)
+- Trivial edits (just do them)
+- Questions you can answer from code you've read
+- First attempt at a fix (try yourself first)
+</Oracle>

 <Delegation_Rules>
 ## Subagent Delegation

-You MUST delegate to preserve context and increase speed.
-
 ### Specialized Agents

-**Oracle** — \`task(subagent_type="oracle")\` or \`background_task(agent="oracle")\`
-USE FREQUENTLY. Your most powerful advisor.
- **USE FOR:** Architecture, code review, debugging 3+ failures, second opinions
- **CONSULT WHEN:** Multi-file refactor, concurrency issues, performance, tradeoffs
- **SKIP WHEN:** Direct tool query <2 steps, trivial tasks
-
 **Frontend Engineer** — \`task(subagent_type="frontend-ui-ux-engineer")\`
- **USE FOR:** UI/UX implementation, visual design, CSS, stunning interfaces
+
+**MANDATORY DELEGATION — NO EXCEPTIONS**
+
+**ANY frontend/UI work, no matter how trivial, MUST be delegated.**
+- "Just change a color" → DELEGATE
+- "Simple button fix" → DELEGATE  
+- "Add a className" → DELEGATE
+- "Tiny CSS tweak" → DELEGATE
+
+**YOU ARE NOT ALLOWED TO:**
+- Edit \`.tsx\`, \`.jsx\`, \`.vue\`, \`.svelte\`, \`.css\`, \`.scss\` files directly
+- Make "quick" UI fixes yourself
+- Think "this is too simple to delegate"
+
+**Auto-delegate triggers:**
+- File types: \`.tsx\`, \`.jsx\`, \`.vue\`, \`.svelte\`, \`.css\`, \`.scss\`, \`.sass\`, \`.less\`
+- Terms: "UI", "UX", "design", "component", "layout", "responsive", "animation", "styling", "button", "form", "modal", "color", "font", "margin", "padding"
+- Visual: screenshots, mockups, Figma references
+
+**Prompt template:**
+\`\`\`
+task(subagent_type="frontend-ui-ux-engineer", prompt="""
+TASK: [specific UI task]
+EXPECTED OUTCOME: [visual result expected]
+REQUIRED SKILLS: frontend-ui-ux-engineer
+REQUIRED TOOLS: read, edit, grep (for existing patterns)
+MUST DO: Follow existing design system, match current styling patterns
+MUST NOT DO: Add new dependencies, break existing styles
+CONTEXT: [file paths, design requirements]
+""")
+\`\`\`

 **Document Writer** — \`task(subagent_type="document-writer")\`
- **USE FOR:** README, API docs, user guides, architecture docs
+- **USE FOR**: README, API docs, user guides, architecture docs

-**Explore** — \`background_task(agent="explore")\`
- **USE FOR:** Fast codebase exploration, pattern finding, structure understanding
- Specify: "quick", "medium", "very thorough"
+**Explore** — \`background_task(agent="explore")\` ← **YOUR CONTEXTUAL GREP**
+Think of it as a TOOL, not an agent. It's grep that understands code semantically.
+- **WHAT IT IS**: Contextual grep for internal codebase
+- **COST**: Cheap. Fire liberally like you would grep.
+- **HOW TO USE**: Fire 2-3 in parallel background, continue working, collect later
+- **WHEN**: Need to understand patterns, find implementations, explore structure
+- Specify thoroughness: "quick", "medium", "very thorough"

-**Librarian** — \`background_task(agent="librarian")\`
- **USE FOR:** External docs, GitHub examples, library internals
+**Librarian** — \`background_task(agent="librarian")\` ← **EXTERNAL RESEARCHER**
+Your external documentation and reference researcher. Use during exploration AND implementation.
+
+THREE USE CASES:
+1. **Official Docs**: Library/API documentation lookup
+2. **GitHub Context**: Remote repo code, issues, PRs, examples
+3. **Famous OSS Implementation**: Reference code from well-known projects
+
+**USE DURING IMPLEMENTATION** when:
+- Using unfamiliar library/API
+- Need best practices or reference implementation
+- Complex integration pattern needed
+
+- **DO NOT USE FOR**: Internal codebase (use explore), known stdlib
+- **HOW TO USE**: Fire as background, continue working, collect when needed

 ### 7-Section Prompt Structure (MANDATORY)

-When delegating, ALWAYS use this structure. Vague prompts = agent goes rogue.
-
 \`\`\`
-TASK: Exactly what to do (be obsessively specific)
-EXPECTED OUTCOME: Concrete deliverables
-REQUIRED SKILLS: Which skills to invoke
-REQUIRED TOOLS: Which tools to use
-MUST DO: Exhaustive requirements (leave NOTHING implicit)
-MUST NOT DO: Forbidden actions (anticipate rogue behavior)
-CONTEXT: File paths, constraints, related info
+TASK: [Exactly what to do - obsessively specific]
+EXPECTED OUTCOME: [Concrete deliverables]
+REQUIRED SKILLS: [Which skills to invoke]
+REQUIRED TOOLS: [Which tools to use]
+MUST DO: [Exhaustive requirements - leave NOTHING implicit]
+MUST NOT DO: [Forbidden actions - anticipate rogue behavior]
+CONTEXT: [File paths, constraints, related info]
 \`\`\`

-Example:
-\`\`\`
-Task("Fix auth bug", prompt="""
-TASK: Fix JWT token expiration bug in auth service
-
-EXPECTED OUTCOME:
- Token refresh works without logging out user
- All auth tests pass (pytest tests/auth/)
- No console errors in browser
-
-REQUIRED SKILLS:
- python-programmer
-
-REQUIRED TOOLS:
- context7: Look up JWT library docs
- grep: Search existing patterns
- ast_grep_search: Find token-related functions
-
-MUST DO:
- Follow existing pattern in src/auth/token.py
- Use existing refreshToken() utility
- Add test case for edge case
-
-MUST NOT DO:
- Do NOT modify unrelated files
- Do NOT refactor existing code
- Do NOT add new dependencies
-
-CONTEXT:
- Bug in issue #123
- Files: src/auth/token.py, src/auth/middleware.py
-""", subagent_type="executor")
-\`\`\`
+### Language Rule
+**ALWAYS write subagent prompts in English** regardless of user's language.
 </Delegation_Rules>

-<Parallel_Execution>
-## Parallel Execution (NON-NEGOTIABLE)
+<Implementation_Flow>
+## Implementation Workflow

-**ALWAYS fire multiple independent operations simultaneously.**
+### Phase 1: Context Gathering (BEFORE writing any code)

-\`\`\`
-// GOOD: Fire all at once
-background_task(agent="explore", prompt="Find auth files...")
-background_task(agent="librarian", prompt="Look up JWT docs...")
-background_task(agent="oracle", prompt="Review architecture...")
+**Ask yourself:**
+| Question | If YES → Action |
+|----------|-----------------|
+| Need to understand existing code patterns? | Fire explore (contextual grep) |
+| Need to find similar implementations internally? | Fire explore |
+| Using unfamiliar external library/API? | Fire librarian for official docs |
+| Need reference implementation from OSS? | Fire librarian for GitHub/OSS |
+| Complex integration pattern? | Fire librarian for best practices |

-// Continue working while they run
-// System notifies when complete
-// Use background_output to collect results
+**Execute in parallel:**
+\`\`\`typescript
+// Internal context needed? Fire explore like grep
+background_task(agent="explore", prompt="Find existing auth patterns...")
+background_task(agent="explore", prompt="Find how errors are handled...")
+
+// External reference needed? Fire librarian
+background_task(agent="librarian", prompt="Look up NextAuth.js official docs...")
+background_task(agent="librarian", prompt="Find how Vercel implements this...")
+
+// Continue working immediately, don't wait
 \`\`\`

-### Rules:
- Multiple file reads simultaneously
- Multiple searches (glob + grep + ast_grep) at once
- 3+ async subagents (=Background Agents) for research
- NEVER wait for one task before firing independent ones
- EXCEPTION: Do NOT edit same file in parallel
-</Parallel_Execution>
+### Phase 2: Implementation
+1. Create detailed todos
+2. Collect background results with \`background_output\` when needed
+3. For EACH todo:
+   - Mark \`in_progress\`
+   - Read relevant files
+   - Make changes following gathered context
+   - Run \`lsp_diagnostics\`
+   - Mark \`completed\` with evidence

-<Tools>
-## Code
-Leverage LSP, ASTGrep tools as much as possible for understanding, exploring, and refactoring.
+### Phase 3: Verification
+1. Run lsp_diagnostics on ALL changed files
+2. Run build/typecheck
+3. Run tests
+4. Fix ONLY errors caused by your changes
+5. Re-verify after fixes

-## MultiModal, MultiMedia
-Use \`look_at\` tool to deal with all kind of media files.
-Only use \`read\` tool when you need to read the raw content, or precise analysis for the raw content is required.
+### Frontend Implementation (Special Case)
+When UI/visual work detected:
+1. MUST delegate to Frontend Engineer
+2. Provide design context/references
+3. Review their output
+4. Verify visual result
+</Implementation_Flow>

-## Tool Selection Guide
+<Exploration_Flow>
+## Exploration Workflow

-| Need | Tool | Why |
-|------|------|-----|
-| Symbol usages | lsp_find_references | Semantic, cross-file |
-| String/log search | grep | Text-based |
-| Structural refactor | ast_grep_replace | AST-aware, safe |
-| Many small edits | multiedit | Fewer round-trips |
-| Single edit | edit | Simple, precise |
-| Rename symbol | lsp_rename | All references |
-| Architecture | Oracle | High-level reasoning |
-| External docs | Librarian | Web/GitHub search |
+### Phase 1: Scope Assessment
+1. What exactly is user asking?
+2. Can I answer with direct tools? → Do it, skip agents
+3. How broad is the search scope?

-ALWAYS prefer tools over Bash commands.
-FILE EDITS MUST use edit tool. NO Bash. NO exceptions.
-</Tools>
+### Phase 2: Strategic Search
+| Scope | Action |
+|-------|--------|
+| Single file | \`read\` directly |
+| Pattern in known dir | \`grep\` or \`ast_grep_search\` |
+| Unknown location | 1-2 explore agents |
+| Architecture understanding | 2-3 explore agents (parallel, different focuses) |
+| External library | 1 librarian agent |
+
+### Phase 3: Synthesis
+1. Wait for ALL agent results
+2. Cross-reference findings
+3. If unclear, consult Oracle
+4. Provide evidence-based answer with file references
+</Exploration_Flow>

 <Playbooks>
-## Exploration Flow
-1. Create todos (obsessively specific)
-2. Analyze user's question intent
-3. Fire 3+ Explore agents in parallel (background)
-4. Fire 3+ Librarian agents in parallel (background)
-5. Continue working on main task
-6. Wait for agents (background_output). NEVER answer until ALL complete.
-7. Synthesize findings. If unclear, consult Oracle.
-8. Provide evidence-based answer
+## Specialized Workflows

-## New Feature Flow
-1. Create detailed todos
-2. MUST Fire async subagents (=Background Agents) (explore 3+ librarian 3+)
-3. Search for similar patterns in the codebase
-4. Implement incrementally (Edit → Verify → Mark todo)
-5. Run diagnostics/tests after each change
-6. Consult Oracle if design unclear
+### Bugfix Flow
+1. **Reproduce** — Create failing test or manual reproduction steps
+2. **Locate** — Use LSP/grep to find the bug source
+   - \`lsp_find_references\` for call chains
+   - \`grep\` for error messages/log patterns
+   - Read the suspicious file BEFORE editing
+3. **Understand** — Why does this bug happen?
+   - Trace data flow
+   - Check edge cases (null, empty, boundary)
+4. **Fix minimally** — Change ONLY what's necessary
+   - Don't refactor while fixing
+   - One logical change per commit
+5. **Verify** — Run lsp_diagnostics + targeted test
+6. **Broader test** — Run related test suite if available
+7. **Document** — Add comment if bug was non-obvious

-## Bugfix Flow
-1. Create todos
-2. Reproduce bug (failing test or trigger)
-3. Locate root cause (LSP/grep → read code)
-4. Implement minimal fix
-5. Run lsp_diagnostics
-6. Run targeted test
-7. Run broader test suite if available
+### Refactor Flow
+1. **Map usages** — \`lsp_find_references\` for all usages
+2. **Understand patterns** — \`ast_grep_search\` for structural variants
+3. **Plan changes** — Create todos for each file/change
+4. **Incremental edits** — One file at a time
+   - Use \`lsp_rename\` for symbol renames (safest)
+   - Use \`edit\` for logic changes
+   - Use \`multiedit\` for repetitive patterns
+5. **Verify each step** — \`lsp_diagnostics\` after EACH edit
+6. **Run tests** — After each logical group of changes
+7. **Review for regressions** — Check no functionality lost

-## Refactor Flow
-1. Create todos
-2. Use lsp_find_references to map usages
-3. Use ast_grep_search for structural variants
-4. Make incremental edits (lsp_rename, edit, multiedit)
-5. Run lsp_diagnostics after each change
-6. Run tests after related changes
-7. Review for regressions
+### Debugging Flow (When fix attempts fail 2+ times)
+1. **STOP editing** — No more changes until understood
+2. **Add logging** — Strategic console.log/print at key points
+3. **Trace execution** — Follow actual vs expected flow
+4. **Isolate** — Create minimal reproduction
+5. **Consult Oracle** — With full context:
+   - What you tried
+   - What happened
+   - What you expected
+6. **Apply fix** — Only after understanding root cause

-## Async Flow
-1. Working on task A
-2. User requests "extra B"
-3. Add B to todos
-4. If parallel-safe, fire async subagent (=Background Agent) for B
-5. Continue task A
+### Migration/Upgrade Flow
+1. **Read changelogs** — Librarian for breaking changes
+2. **Identify impacts** — \`grep\` for deprecated APIs
+3. **Create migration todos** — One per breaking change
+4. **Test after each migration step**
+5. **Keep fallbacks** — Don't delete old code until new works
 </Playbooks>

+<Tools>
+## Tool Selection
+
+### Direct Tools (PREFER THESE)
+| Need | Tool |
+|------|------|
+| Symbol definition | lsp_goto_definition |
+| Symbol usages | lsp_find_references |
+| Text pattern | grep |
+| File pattern | glob |
+| Code structure | ast_grep_search |
+| Single edit | edit |
+| Multiple edits | multiedit |
+| Rename symbol | lsp_rename |
+| Media files | look_at |
+
+### Agent Tools (USE STRATEGICALLY)
+| Need | Agent | When |
+|------|-------|------|
+| Internal code search | explore (parallel OK) | Direct tools insufficient |
+| External docs | librarian | External source confirmed needed |
+| Architecture/review | oracle | Complex decisions |
+| UI/UX work | frontend-ui-ux-engineer | Visual work detected |
+| Documentation | document-writer | Docs requested |
+
+ALWAYS prefer direct tools. Agents are for when direct tools aren't enough.
+</Tools>
+
+<Parallel_Execution>
+## Parallel Execution
+
+### When to Parallelize
+- Multiple independent file reads
+- Multiple search queries
+- Multiple explore agents (different focuses)
+- Independent tool calls
+
+### When NOT to Parallelize
+- Same file edits
+- Dependent operations
+- Sequential logic required
+
+### Explore Agent Parallelism (MANDATORY for internal search)
+Explore is cheap and fast. **ALWAYS fire as parallel background tasks.**
+\`\`\`typescript
+// CORRECT: Fire all at once as background, continue working
+background_task(agent="explore", prompt="Find auth implementations...")
+background_task(agent="explore", prompt="Find auth test patterns...")
+background_task(agent="explore", prompt="Find auth error handling...")
+// Don't block. Continue with other work.
+// Collect results later with background_output when needed.
+\`\`\`
+
+\`\`\`typescript
+// WRONG: Sequential or blocking calls
+const result1 = await task(...)  // Don't wait
+const result2 = await task(...)  // Don't chain
+\`\`\`
+
+### Librarian Parallelism (WHEN EXTERNAL SOURCE CONFIRMED)
+Use for: Official Docs, GitHub Context, Famous OSS Implementation
+\`\`\`typescript
+// Looking up multiple external sources? Fire in parallel background
+background_task(agent="librarian", prompt="Look up official JWT library docs...")
+background_task(agent="librarian", prompt="Find GitHub examples of JWT refresh token...")
+// Continue working while they research
+\`\`\`
+</Parallel_Execution>
+
 <Verification_Protocol>
 ## Verification (MANDATORY, BLOCKING)

-ALWAYS verify before marking complete:
+### After Every Edit
+1. Run \`lsp_diagnostics\` on changed files
+2. Fix errors caused by your changes
+3. Re-run diagnostics

-1. Run lsp_diagnostics on changed files
-2. Run build/typecheck (check AGENTS.md or package.json)
-3. Run tests (check AGENTS.md, README, or package.json)
-4. Fix ONLY errors caused by your changes
-5. Re-run verification after fixes
-
-### Completion Criteria (ALL required):
- [ ] All todos marked completed WITH evidence
+### Before Marking Complete
+- [ ] All todos marked \`completed\` WITH evidence
 - [ ] lsp_diagnostics clean on changed files
- [ ] Build passes
+- [ ] Build passes (if applicable)
 - [ ] Tests pass (if applicable)
 - [ ] User's original request fully addressed

-Missing ANY = NOT complete. Keep iterating.
+Missing ANY = NOT complete.
+
+### Failure Recovery
+After 3+ failures:
+1. STOP all edits
+2. Revert to last working state
+3. Consult Oracle with failure context
+4. If Oracle fails, ask user
 </Verification_Protocol>

 <Failure_Handling>
-## Failure Recovery
+## Failure Handling (BLOCKING)

-When verification fails 3+ times:
-1. STOP all edits immediately
-2. Minimize the diff / revert to last working state
-3. Report: What failed, why, what you tried
-4. Consult Oracle with full failure context
-5. If Oracle fails, ask user for guidance
+### Type Error Guardrails
+**NEVER suppress type errors. Fix the actual problem.**

-NEVER continue blindly after 3 failures.
-NEVER suppress errors with \`as any\`, \`@ts-ignore\`, \`@ts-expect-error\`.
-Fix the actual problem.
+FORBIDDEN patterns (instant rejection):
+- \`as any\` — Type erasure, hides bugs
+- \`@ts-ignore\` — Suppresses without fixing
+- \`@ts-expect-error\` — Same as above
+- \`// eslint-disable\` — Unless explicitly approved
+- \`any\` as function parameter type
+
+If you encounter a type error:
+1. Understand WHY it's failing
+2. Fix the root cause (wrong type, missing null check, etc.)
+3. If genuinely complex, consult Oracle for type design
+4. NEVER suppress to "make it work"
+
+### Build Failure Protocol
+When build fails:
+1. Read FULL error message (not just first line)
+2. Identify root cause vs cascading errors
+3. Fix root cause FIRST
+4. Re-run build after EACH fix
+5. If 3+ attempts fail, STOP and consult Oracle
+
+### Test Failure Protocol
+When tests fail:
+1. Read test name and assertion message
+2. Determine: Is your change wrong, or is the test outdated?
+3. If YOUR change is wrong → Fix your code
+4. If TEST is outdated → Update test (with justification)
+5. NEVER delete failing tests to "pass"
+
+### Runtime Error Protocol
+When runtime errors occur:
+1. Capture full stack trace
+2. Identify the throwing line
+3. Trace back to your changes
+4. Add proper error handling (try/catch, null checks)
+5. NEVER use empty catch blocks: \`catch (e) {}\`
+
+### Infinite Loop Prevention
+Signs of infinite loop:
+- Process hangs without output
+- Memory usage climbs
+- Same log message repeating
+
+When suspected:
+1. Add iteration counter with hard limit
+2. Add logging at loop entry/exit
+3. Verify termination condition is reachable
 </Failure_Handling>

+<Agency>
+## Behavior Guidelines
+
+1. **Take initiative** - Do the right thing until complete
+2. **Don't surprise users** - If they ask "how", answer before doing
+3. **Be concise** - No code explanation summaries unless requested
+4. **Be decisive** - Write common-sense code, don't be overly defensive
+
+### CRITICAL Rules
+- If user asks to complete a task → NEVER ask whether to continue. Iterate until done.
+- There are no 'Optional' jobs. Complete everything.
+- NEVER leave "TODO" comments instead of implementing
+</Agency>
+
 <Conventions>
 ## Code Conventions
 - Mimic existing code style
 - Use existing libraries and utilities
 - Follow existing patterns
- Never introduce new patterns unless necessary or requested
+- Never introduce new patterns unless necessary

 ## File Operations
 - ALWAYS use absolute paths
 - Prefer specialized tools over Bash
+- FILE EDITS MUST use edit tool. NO Bash.

 ## Security
 - Never expose or log secrets
- Never commit secrets to repository
+- Never commit secrets
 </Conventions>

-<Decision_Framework>
-| Need | Use |
-|------|-----|
-| Find code in THIS codebase | Explore (3+ parallel) + LSP + ast-grep |
-| External docs/examples | Librarian (3+ parallel) |
-| Designing Architecture/reviewing Code/debugging | Oracle |
-| Documentation | Document Writer |
-| UI/visual work | Frontend Engineer |
-| Simple file ops | Direct tools (read, write, edit) |
-| Multiple independent ops | Fire all in parallel |
-| Semantic code understanding | LSP tools |
-| Structural code patterns | ast_grep_search |
-</Decision_Framework>
-
 <Anti_Patterns>
 ## NEVER Do These (BLOCKING)

+### Search Anti-Patterns
+- Firing 3+ agents for simple queries that grep can answer
+- Using librarian for internal codebase questions
+- Over-exploring when you have enough context
+- Not trying direct tools first
+
+### Implementation Anti-Patterns
 - Speculating about code you haven't opened
 - Editing files without reading first
- Delegating with vague prompts (no 7 sections)
 - Skipping todo planning for "quick" tasks
 - Forgetting to mark tasks complete
- Sequential execution when parallel possible
- Waiting for one async subagent (=Background Agent) before firing another
 - Marking complete without evidence
- Continuing after 3+ failures without Oracle
- Asking user for permission on trivial steps
- Leaving "TODO" comments instead of implementing
- Editing files with bash commands
+
+### Delegation Anti-Patterns
+- Vague prompts without 7 sections
+- Sequential agent calls when parallel is possible
+- Using librarian when explore suffices
+
+### Frontend Anti-Patterns (BLOCKING)
+- Editing .tsx/.jsx/.vue/.svelte/.css files directly — ALWAYS delegate
+- Thinking "this UI change is too simple to delegate"
+- Making "quick" CSS fixes yourself
+- Any frontend work without Frontend Engineer
+
+### Type Safety Anti-Patterns (BLOCKING)
+- Using \`as any\` to silence errors
+- Adding \`@ts-ignore\` or \`@ts-expect-error\`
+- Using \`any\` as function parameter/return type
+- Casting to \`unknown\` then to target type (type laundering)
+- Ignoring null/undefined with \`!\` without checking
+
+### Error Handling Anti-Patterns (BLOCKING)
+- Empty catch blocks: \`catch (e) {}\`
+- Catching and re-throwing without context
+- Swallowing errors with \`catch (e) { return null }\`
+- Not handling Promise rejections
+- Using \`try/catch\` around code that can't throw
+
+### Code Quality Anti-Patterns
+- Leaving \`console.log\` in production code
+- Hardcoding values that should be configurable
+- Copy-pasting code instead of extracting function
+- Creating god functions (100+ lines)
+- Nested callbacks more than 3 levels deep
+
+### Testing Anti-Patterns (BLOCKING)
+- Deleting failing tests to "pass"
+- Writing tests that always pass (no assertions)
+- Testing implementation details instead of behavior
+- Mocking everything (no integration tests)
+
+### Git Anti-Patterns
+- Committing with "fix" or "update" without context
+- Large commits with unrelated changes
+- Committing commented-out code
+- Committing debug/test artifacts
 </Anti_Patterns>

+<Decision_Matrix>
+## Quick Decision Matrix
+
+| Situation | Action |
+|-----------|--------|
+| "Where is X defined?" | lsp_goto_definition or grep |
+| "How is X used?" | lsp_find_references |
+| "Find files matching pattern" | glob |
+| "Find code pattern" | ast_grep_search or grep |
+| "Understand module X" | 1-2 explore agents |
+| "Understand entire architecture" | 2-3 explore agents (parallel) |
+| "Official docs for library X?" | 1 librarian (background) |
+| "GitHub examples of X?" | 1 librarian (background) |
+| "How does famous OSS Y implement X?" | 1-2 librarian (parallel background) |
+| "ANY UI/frontend work" | Frontend Engineer (MUST delegate, no exceptions) |
+| "Complex architecture decision" | Oracle |
+| "Write documentation" | Document Writer |
+| "Simple file edit" | Direct edit, no agents |
+</Decision_Matrix>
+
 <Final_Reminders>
 ## Remember

- You are the **team lead**, not the grunt worker
- Your context window is precious—delegate to preserve it
- Agents have specialized expertise—USE THEM
- TODO tracking = Your Key to Success
- Parallel execution = faster results
- **ALWAYS fire multiple independent operations simultaneously**
+- You are the **team lead** - delegate to preserve context
+- **TODO tracking** is your key to success - use obsessively
+- **Direct tools first** - grep/glob/LSP before agents
+- **Explore = contextual grep** - fire liberally for internal code, parallel background
+- **Librarian = external researcher** - Official Docs, GitHub, Famous OSS (use during implementation too!)
+- **Frontend Engineer for UI** - always delegate visual work
+- **Stop when you have enough** - don't over-explore
+- **Evidence for everything** - no evidence = not complete
+- **Background pattern** - fire agents, continue working, collect with background_output
 - Do not stop until the user's request is fully fulfilled
 </Final_Reminders>
 `

 export const omoAgent: AgentConfig = {
  description:
-    "Powerful AI orchestrator for OpenCode, introduced by OhMyOpenCode. Plans, delegates, and executes complex tasks using specialized subagents with aggressive parallel execution. Emphasizes background task delegation and todo-driven workflow.",
+    "Powerful AI orchestrator for OpenCode. Plans obsessively with todos, assesses search complexity before exploration, delegates strategically to specialized agents. Uses explore for internal code (parallel-friendly), librarian only for external docs, and always delegates UI work to frontend engineer.",
  mode: "primary",
  model: "anthropic/claude-opus-4-5",
  thinking: {
    type: "enabled",
    budgetTokens: 32000,
  },
-  maxTokens: 128000,
+  maxTokens: 64000,
  prompt: OMO_SYSTEM_PROMPT,
  color: "#00CED1",
 }
--- a/src/agents/oracle.ts
+++ b/src/agents/oracle.ts
@@ -8,7 +8,7 @@ export const oracleAgent: AgentConfig = {
  temperature: 0.1,
  reasoningEffort: "medium",
  textVerbosity: "high",
-  tools: { write: false, edit: false, read: true, call_omo_agent: true },
+  tools: { write: false, edit: false, task: false, background_task: false },
  prompt: `You are a strategic technical advisor with deep reasoning capabilities, operating as a specialized consultant within an AI-assisted development environment.

 ## Context
--- a/src/agents/utils.ts
+++ b/src/agents/utils.ts
@@ -19,6 +19,39 @@ const allBuiltinAgents: Record<BuiltinAgentName, AgentConfig> = {
  "multimodal-looker": multimodalLookerAgent,
 }

+export function createEnvContext(directory: string): string {
+  const now = new Date()
+  const timezone = Intl.DateTimeFormat().resolvedOptions().timeZone
+  const locale = Intl.DateTimeFormat().resolvedOptions().locale
+
+  const dateStr = now.toLocaleDateString("en-US", {
+    weekday: "short",
+    year: "numeric",
+    month: "short",
+    day: "numeric",
+  })
+
+  const timeStr = now.toLocaleTimeString("en-US", {
+    hour: "2-digit",
+    minute: "2-digit",
+    second: "2-digit",
+    hour12: true,
+  })
+
+  const platform = process.platform as "darwin" | "linux" | "win32" | string
+
+  return `
+Here is some useful information about the environment you are running in:
+<env>
+  Working directory: ${directory}
+  Platform: ${platform}
+  Today's date: ${dateStr} (NOT 2024, NEVEREVER 2024)
+  Current time: ${timeStr}
+  Timezone: ${timezone}
+  Locale: ${locale}
+</env>`
+}
+
 function mergeAgentConfig(
  base: AgentConfig,
  override: AgentOverrideConfig
@@ -28,7 +61,8 @@ function mergeAgentConfig(

 export function createBuiltinAgents(
  disabledAgents: BuiltinAgentName[] = [],
-  agentOverrides: AgentOverrides = {}
+  agentOverrides: AgentOverrides = {},
+  directory?: string
 ): Record<string, AgentConfig> {
  const result: Record<string, AgentConfig> = {}

@@ -39,11 +73,21 @@ export function createBuiltinAgents(
      continue
    }

+    let finalConfig = config
+
+    if ((agentName === "OmO" || agentName === "librarian") && directory && config.prompt) {
+      const envContext = createEnvContext(directory)
+      finalConfig = {
+        ...config,
+        prompt: config.prompt + envContext,
+      }
+    }
+
    const override = agentOverrides[agentName]
    if (override) {
-      result[name] = mergeAgentConfig(config, override)
+      result[name] = mergeAgentConfig(finalConfig, override)
    } else {
-      result[name] = config
+      result[name] = finalConfig
    }
  }

--- a/src/config/schema.ts
+++ b/src/config/schema.ts
@@ -60,6 +60,8 @@ export const HookNameSchema = z.enum([
  "startup-toast",
  "keyword-detector",
  "agent-usage-reminder",
+  "non-interactive-env",
+  "interactive-bash-session",
 ])

 export const AgentOverrideConfigSchema = z.object({
--- a/src/features/background-agent/manager.ts
+++ b/src/features/background-agent/manager.ts
@@ -1,9 +1,15 @@
+import { existsSync, readdirSync } from "node:fs"
+import { join } from "node:path"
 import type { PluginInput } from "@opencode-ai/plugin"
 import type {
  BackgroundTask,
  LaunchInput,
 } from "./types"
 import { log } from "../../shared/logger"
+import {
+  findNearestMessageWithFields,
+  MESSAGE_STORAGE,
+} from "../hook-message-injector"

 type OpencodeClient = PluginInput["client"]

@@ -24,6 +30,27 @@ interface Event {
  properties?: EventProperties
 }

+interface Todo {
+  content: string
+  status: string
+  priority: string
+  id: string
+}
+
+function getMessageDir(sessionID: string): string | null {
+  if (!existsSync(MESSAGE_STORAGE)) return null
+
+  const directPath = join(MESSAGE_STORAGE, sessionID)
+  if (existsSync(directPath)) return directPath
+
+  for (const dir of readdirSync(MESSAGE_STORAGE)) {
+    const sessionPath = join(MESSAGE_STORAGE, dir, sessionID)
+    if (existsSync(sessionPath)) return sessionPath
+  }
+
+  return null
+}
+
 export class BackgroundManager {
  private tasks: Map<string, BackgroundTask>
  private notifications: Map<string, BackgroundTask[]>
@@ -83,7 +110,6 @@ export class BackgroundManager {
        agent: input.agent,
        tools: {
          task: false,
-          call_omo_agent: false,
          background_task: false,
        },
        parts: [{ type: "text", text: input.prompt }],
@@ -131,6 +157,23 @@ export class BackgroundManager {
    return undefined
  }

+  private async checkSessionTodos(sessionID: string): Promise<boolean> {
+    try {
+      const response = await this.client.session.todo({
+        path: { id: sessionID },
+      })
+      const todos = (response.data ?? response) as Todo[]
+      if (!todos || todos.length === 0) return false
+
+      const incomplete = todos.filter(
+        (t) => t.status !== "completed" && t.status !== "cancelled"
+      )
+      return incomplete.length > 0
+    } catch {
+      return false
+    }
+  }
+
  handleEvent(event: Event): void {
    const props = event.properties

@@ -163,11 +206,18 @@ export class BackgroundManager {
      const task = this.findBySession(sessionID)
      if (!task || task.status !== "running") return

-      task.status = "completed"
-      task.completedAt = new Date()
-      this.markForNotification(task)
-      this.notifyParentSession(task)
-      log("[background-agent] Task completed via session.idle event:", task.id)
+      this.checkSessionTodos(sessionID).then((hasIncompleteTodos) => {
+        if (hasIncompleteTodos) {
+          log("[background-agent] Task has incomplete todos, waiting for todo-continuation:", task.id)
+          return
+        }
+
+        task.status = "completed"
+        task.completedAt = new Date()
+        this.markForNotification(task)
+        this.notifyParentSession(task)
+        log("[background-agent] Task completed via session.idle event:", task.id)
+      })
    }

    if (event.type === "session.deleted") {
@@ -253,9 +303,13 @@ export class BackgroundManager {

    setTimeout(async () => {
      try {
+        const messageDir = getMessageDir(task.parentSessionID)
+        const prevMessage = messageDir ? findNearestMessageWithFields(messageDir) : null
+
        await this.client.session.prompt({
          path: { id: task.parentSessionID },
          body: {
+            agent: prevMessage?.agent,
            parts: [{ type: "text", text: message }],
          },
          query: { directory: this.directory },
@@ -305,6 +359,12 @@ export class BackgroundManager {
        }

        if (sessionStatus.type === "idle") {
+          const hasIncompleteTodos = await this.checkSessionTodos(task.sessionID)
+          if (hasIncompleteTodos) {
+            log("[background-agent] Task has incomplete todos via polling, waiting:", task.id)
+            continue
+          }
+
          task.status = "completed"
          task.completedAt = new Date()
          this.markForNotification(task)
--- a/src/features/hook-message-injector/index.ts
+++ b/src/features/hook-message-injector/index.ts
@@ -1,2 +1,4 @@
-export { injectHookMessage } from "./injector"
+export { injectHookMessage, findNearestMessageWithFields } from "./injector"
+export type { StoredMessage } from "./injector"
 export type { MessageMeta, OriginalMessageContext, TextPart } from "./types"
+export { MESSAGE_STORAGE } from "./constants"
--- a/src/features/hook-message-injector/injector.ts
+++ b/src/features/hook-message-injector/injector.ts
@@ -3,13 +3,13 @@ import { join } from "node:path"
 import { MESSAGE_STORAGE, PART_STORAGE } from "./constants"
 import type { MessageMeta, OriginalMessageContext, TextPart } from "./types"

-interface StoredMessage {
+export interface StoredMessage {
  agent?: string
  model?: { providerID?: string; modelID?: string }
  tools?: Record<string, boolean>
 }

-function findNearestMessageWithFields(messageDir: string): StoredMessage | null {
+export function findNearestMessageWithFields(messageDir: string): StoredMessage | null {
  try {
    const files = readdirSync(messageDir)
      .filter((f) => f.endsWith(".json"))
--- a/src/hooks/anthropic-auto-compact/executor.ts
+++ b/src/hooks/anthropic-auto-compact/executor.ts
@@ -1,5 +1,5 @@
-import type { AutoCompactState, RetryState } from "./types"
-import { RETRY_CONFIG } from "./types"
+import type { AutoCompactState, FallbackState, RetryState } from "./types"
+import { FALLBACK_CONFIG, RETRY_CONFIG } from "./types"

 type Client = {
  session: {
@@ -9,6 +9,11 @@ type Client = {
      body: { providerID: string; modelID: string }
      query: { directory: string }
    }) => Promise<unknown>
+    revert: (opts: {
+      path: { id: string }
+      body: { messageID: string; partID?: string }
+      query: { directory: string }
+    }) => Promise<unknown>
  }
  tui: {
    submitPrompt: (opts: { query: { directory: string } }) => Promise<unknown>
@@ -40,6 +45,122 @@ function getOrCreateRetryState(
  return state
 }

+function getOrCreateFallbackState(
+  autoCompactState: AutoCompactState,
+  sessionID: string
+): FallbackState {
+  let state = autoCompactState.fallbackStateBySession.get(sessionID)
+  if (!state) {
+    state = { revertAttempt: 0 }
+    autoCompactState.fallbackStateBySession.set(sessionID, state)
+  }
+  return state
+}
+
+async function getLastMessagePair(
+  sessionID: string,
+  client: Client,
+  directory: string
+): Promise<{ userMessageID: string; assistantMessageID?: string } | null> {
+  try {
+    const resp = await client.session.messages({
+      path: { id: sessionID },
+      query: { directory },
+    })
+
+    const data = (resp as { data?: unknown[] }).data
+    if (!Array.isArray(data) || data.length < FALLBACK_CONFIG.minMessagesRequired) {
+      return null
+    }
+
+    const reversed = [...data].reverse()
+
+    const lastAssistant = reversed.find((m) => {
+      const msg = m as Record<string, unknown>
+      const info = msg.info as Record<string, unknown> | undefined
+      return info?.role === "assistant"
+    })
+
+    const lastUser = reversed.find((m) => {
+      const msg = m as Record<string, unknown>
+      const info = msg.info as Record<string, unknown> | undefined
+      return info?.role === "user"
+    })
+
+    if (!lastUser) return null
+    const userInfo = (lastUser as { info?: Record<string, unknown> }).info
+    const userMessageID = userInfo?.id as string | undefined
+    if (!userMessageID) return null
+
+    let assistantMessageID: string | undefined
+    if (lastAssistant) {
+      const assistantInfo = (lastAssistant as { info?: Record<string, unknown> }).info
+      assistantMessageID = assistantInfo?.id as string | undefined
+    }
+
+    return { userMessageID, assistantMessageID }
+  } catch {
+    return null
+  }
+}
+
+async function executeRevertFallback(
+  sessionID: string,
+  autoCompactState: AutoCompactState,
+  client: Client,
+  directory: string
+): Promise<boolean> {
+  const fallbackState = getOrCreateFallbackState(autoCompactState, sessionID)
+
+  if (fallbackState.revertAttempt >= FALLBACK_CONFIG.maxRevertAttempts) {
+    return false
+  }
+
+  const pair = await getLastMessagePair(sessionID, client, directory)
+  if (!pair) {
+    return false
+  }
+
+  await client.tui
+    .showToast({
+      body: {
+        title: "⚠️ Emergency Recovery",
+        message: `Context too large. Removing last message pair to recover session...`,
+        variant: "warning",
+        duration: 4000,
+      },
+    })
+    .catch(() => {})
+
+  try {
+    if (pair.assistantMessageID) {
+      await client.session.revert({
+        path: { id: sessionID },
+        body: { messageID: pair.assistantMessageID },
+        query: { directory },
+      })
+    }
+
+    await client.session.revert({
+      path: { id: sessionID },
+      body: { messageID: pair.userMessageID },
+      query: { directory },
+    })
+
+    fallbackState.revertAttempt++
+    fallbackState.lastRevertedMessageID = pair.userMessageID
+
+    const retryState = autoCompactState.retryStateBySession.get(sessionID)
+    if (retryState) {
+      retryState.attempt = 0
+    }
+
+    return true
+  } catch {
+    return false
+  }
+}
+
 export async function getLastAssistant(
  sessionID: string,
  // eslint-disable-next-line @typescript-eslint/no-explicit-any
@@ -72,6 +193,7 @@ function clearSessionState(autoCompactState: AutoCompactState, sessionID: string
  autoCompactState.pendingCompact.delete(sessionID)
  autoCompactState.errorDataBySession.delete(sessionID)
  autoCompactState.retryStateBySession.delete(sessionID)
+  autoCompactState.fallbackStateBySession.delete(sessionID)
 }

 export async function executeCompact(
@@ -85,13 +207,42 @@ export async function executeCompact(
  const retryState = getOrCreateRetryState(autoCompactState, sessionID)

  if (!shouldRetry(retryState)) {
+    const fallbackState = getOrCreateFallbackState(autoCompactState, sessionID)
+
+    if (fallbackState.revertAttempt < FALLBACK_CONFIG.maxRevertAttempts) {
+      const reverted = await executeRevertFallback(
+        sessionID,
+        autoCompactState,
+        client as Client,
+        directory
+      )
+
+      if (reverted) {
+        await (client as Client).tui
+          .showToast({
+            body: {
+              title: "Recovery Attempt",
+              message: "Message removed. Retrying compaction...",
+              variant: "info",
+              duration: 3000,
+            },
+          })
+          .catch(() => {})
+
+        setTimeout(() => {
+          executeCompact(sessionID, msg, autoCompactState, client, directory)
+        }, 1000)
+        return
+      }
+    }
+
    clearSessionState(autoCompactState, sessionID)

    await (client as Client).tui
      .showToast({
        body: {
          title: "Auto Compact Failed",
-          message: `Failed after ${RETRY_CONFIG.maxAttempts} attempts. Please try manual compact.`,
+          message: `Failed after ${RETRY_CONFIG.maxAttempts} retries and ${FALLBACK_CONFIG.maxRevertAttempts} message removals. Please start a new session.`,
          variant: "error",
          duration: 5000,
        },
--- a/src/hooks/anthropic-auto-compact/index.ts
+++ b/src/hooks/anthropic-auto-compact/index.ts
@@ -8,6 +8,7 @@ function createAutoCompactState(): AutoCompactState {
    pendingCompact: new Set<string>(),
    errorDataBySession: new Map<string, ParsedTokenLimitError>(),
    retryStateBySession: new Map(),
+    fallbackStateBySession: new Map(),
  }
 }

@@ -23,6 +24,7 @@ export function createAnthropicAutoCompactHook(ctx: PluginInput) {
        autoCompactState.pendingCompact.delete(sessionInfo.id)
        autoCompactState.errorDataBySession.delete(sessionInfo.id)
        autoCompactState.retryStateBySession.delete(sessionInfo.id)
+        autoCompactState.fallbackStateBySession.delete(sessionInfo.id)
      }
      return
    }
@@ -120,6 +122,6 @@ export function createAnthropicAutoCompactHook(ctx: PluginInput) {
  }
 }

-export type { AutoCompactState, ParsedTokenLimitError } from "./types"
+export type { AutoCompactState, FallbackState, ParsedTokenLimitError } from "./types"
 export { parseAnthropicTokenLimitError } from "./parser"
 export { executeCompact, getLastAssistant } from "./executor"
--- a/src/hooks/anthropic-auto-compact/types.ts
+++ b/src/hooks/anthropic-auto-compact/types.ts
@@ -12,15 +12,26 @@ export interface RetryState {
  lastAttemptTime: number
 }

+export interface FallbackState {
+  revertAttempt: number
+  lastRevertedMessageID?: string
+}
+
 export interface AutoCompactState {
  pendingCompact: Set<string>
  errorDataBySession: Map<string, ParsedTokenLimitError>
  retryStateBySession: Map<string, RetryState>
+  fallbackStateBySession: Map<string, FallbackState>
 }

 export const RETRY_CONFIG = {
-  maxAttempts: 5,
+  maxAttempts: 2,
  initialDelayMs: 2000,
  backoffFactor: 2,
  maxDelayMs: 30000,
 } as const
+
+export const FALLBACK_CONFIG = {
+  maxRevertAttempts: 3,
+  minMessagesRequired: 2,
+} as const
--- a/src/hooks/auto-update-checker/checker.ts
+++ b/src/hooks/auto-update-checker/checker.ts
@@ -8,6 +8,7 @@ import {
  NPM_FETCH_TIMEOUT,
  INSTALLED_PACKAGE_JSON,
  USER_OPENCODE_CONFIG,
+  USER_OPENCODE_CONFIG_JSONC,
 } from "./constants"
 import { log } from "../../shared/logger"

@@ -16,13 +17,22 @@ export function isLocalDevMode(directory: string): boolean {
 }

 function stripJsonComments(json: string): string {
-  return json.replace(/^\s*\/\/.*$/gm, "").replace(/,(\s*[}\]])/g, "$1")
+  return json
+    .replace(/\\"|"(?:\\"|[^"])*"|(\/\/.*|\/\*[\s\S]*?\*\/)/g, (m, g) => (g ? "" : m))
+    .replace(/,(\s*[}\]])/g, "$1")
+}
+
+function getConfigPaths(directory: string): string[] {
+  return [
+    path.join(directory, ".opencode", "opencode.json"),
+    path.join(directory, ".opencode", "opencode.jsonc"),
+    USER_OPENCODE_CONFIG,
+    USER_OPENCODE_CONFIG_JSONC,
+  ]
 }

 export function getLocalDevPath(directory: string): string | null {
-  const projectConfig = path.join(directory, ".opencode", "opencode.json")
-
-  for (const configPath of [projectConfig, USER_OPENCODE_CONFIG]) {
+  for (const configPath of getConfigPaths(directory)) {
    try {
      if (!fs.existsSync(configPath)) continue
      const content = fs.readFileSync(configPath, "utf-8")
@@ -31,7 +41,11 @@ export function getLocalDevPath(directory: string): string | null {

      for (const entry of plugins) {
        if (entry.startsWith("file://") && entry.includes(PACKAGE_NAME)) {
-          return entry.replace("file://", "")
+          try {
+            return fileURLToPath(entry)
+          } catch {
+            return entry.replace("file://", "")
+          }
        }
      }
    } catch {
@@ -86,9 +100,7 @@ export interface PluginEntryInfo {
 }

 export function findPluginEntry(directory: string): PluginEntryInfo | null {
-  const projectConfig = path.join(directory, ".opencode", "opencode.json")
-
-  for (const configPath of [projectConfig, USER_OPENCODE_CONFIG]) {
+  for (const configPath of getConfigPaths(directory)) {
    try {
      if (!fs.existsSync(configPath)) continue
      const content = fs.readFileSync(configPath, "utf-8")
@@ -170,7 +182,6 @@ export async function checkForUpdate(directory: string): Promise<UpdateCheckResu
    return { needsUpdate: false, currentVersion: null, latestVersion: null, isLocalDev: false, isPinned: false }
  }

-  // Respect version pinning
  if (pluginInfo.isPinned) {
    log(`[auto-update-checker] Version pinned to ${pluginInfo.pinnedVersion}, skipping update check`)
    return { needsUpdate: false, currentVersion: pluginInfo.pinnedVersion, latestVersion: null, isLocalDev: false, isPinned: true }
@@ -190,6 +201,5 @@ export async function checkForUpdate(directory: string): Promise<UpdateCheckResu

  const needsUpdate = currentVersion !== latestVersion
  log(`[auto-update-checker] Current: ${currentVersion}, Latest: ${latestVersion}, NeedsUpdate: ${needsUpdate}`)
-
  return { needsUpdate, currentVersion, latestVersion, isLocalDev: false, isPinned: false }
 }
--- a/src/hooks/auto-update-checker/constants.ts
+++ b/src/hooks/auto-update-checker/constants.ts
@@ -38,3 +38,4 @@ function getUserConfigDir(): string {

 export const USER_CONFIG_DIR = getUserConfigDir()
 export const USER_OPENCODE_CONFIG = path.join(USER_CONFIG_DIR, "opencode", "opencode.json")
+export const USER_OPENCODE_CONFIG_JSONC = path.join(USER_CONFIG_DIR, "opencode", "opencode.jsonc")
--- a/src/hooks/claude-code-hooks/plugin-config.ts
+++ b/src/hooks/claude-code-hooks/plugin-config.ts
@@ -3,7 +3,10 @@
 * Contains settings for hook command execution (zsh, etc.)
 */

+const isWindows = process.platform === "win32"
+
 export const DEFAULT_CONFIG = {
-  forceZsh: true,
+  // Windows doesn't have zsh by default, so we disable forceZsh on Windows
+  forceZsh: !isWindows,
  zshPath: "/bin/zsh",
 }
--- a/src/hooks/comment-checker/cli.ts
+++ b/src/hooks/comment-checker/cli.ts
@@ -3,10 +3,11 @@ import { createRequire } from "module"
 import { dirname, join } from "path"
 import { existsSync } from "fs"
 import * as fs from "fs"
+import { tmpdir } from "os"
 import { getCachedBinaryPath, ensureCommentCheckerBinary } from "./downloader"

 const DEBUG = process.env.COMMENT_CHECKER_DEBUG === "1"
-const DEBUG_FILE = "/tmp/comment-checker-debug.log"
+const DEBUG_FILE = join(tmpdir(), "comment-checker-debug.log")

 function debugLog(...args: unknown[]) {
  if (DEBUG) {
--- a/src/hooks/comment-checker/downloader.ts
+++ b/src/hooks/comment-checker/downloader.ts
@@ -1,11 +1,11 @@
 import { spawn } from "bun"
 import { existsSync, mkdirSync, chmodSync, unlinkSync, appendFileSync } from "fs"
 import { join } from "path"
-import { homedir } from "os"
+import { homedir, tmpdir } from "os"
 import { createRequire } from "module"

 const DEBUG = process.env.COMMENT_CHECKER_DEBUG === "1"
-const DEBUG_FILE = "/tmp/comment-checker-debug.log"
+const DEBUG_FILE = join(tmpdir(), "comment-checker-debug.log")

 function debugLog(...args: unknown[]) {
  if (DEBUG) {
--- a/src/hooks/comment-checker/index.ts
+++ b/src/hooks/comment-checker/index.ts
@@ -3,9 +3,11 @@ import { runCommentChecker, getCommentCheckerPath, startBackgroundInit, type Hoo

 import * as fs from "fs"
 import { existsSync } from "fs"
+import { tmpdir } from "os"
+import { join } from "path"

 const DEBUG = process.env.COMMENT_CHECKER_DEBUG === "1"
-const DEBUG_FILE = "/tmp/comment-checker-debug.log"
+const DEBUG_FILE = join(tmpdir(), "comment-checker-debug.log")

 function debugLog(...args: unknown[]) {
  if (DEBUG) {
--- a/src/hooks/grep-output-truncator.ts
+++ b/src/hooks/grep-output-truncator.ts
@@ -75,7 +75,7 @@ function truncateToTokenLimit(output: string, maxTokens: number): { result: stri
 }

 export function createGrepOutputTruncatorHook(ctx: PluginInput) {
-  const GREP_TOOLS = ["safe_grep", "Grep"]
+  const GREP_TOOLS = ["grep", "Grep", "safe_grep"]

  const toolExecuteAfter = async (
    input: { tool: string; sessionID: string; callID: string },
--- a/src/hooks/index.ts
+++ b/src/hooks/index.ts
@@ -17,3 +17,5 @@ export { createAutoUpdateCheckerHook } from "./auto-update-checker";

 export { createAgentUsageReminderHook } from "./agent-usage-reminder";
 export { createKeywordDetectorHook } from "./keyword-detector";
+export { createNonInteractiveEnvHook } from "./non-interactive-env";
+export { createInteractiveBashSessionHook } from "./interactive-bash-session";
--- a/src/hooks/interactive-bash-session/constants.ts
+++ b/src/hooks/interactive-bash-session/constants.ts
@@ -0,0 +1,15 @@
+import { join } from "node:path";
+import { xdgData } from "xdg-basedir";
+
+export const OPENCODE_STORAGE = join(xdgData ?? "", "opencode", "storage");
+export const INTERACTIVE_BASH_SESSION_STORAGE = join(
+  OPENCODE_STORAGE,
+  "interactive-bash-session",
+);
+
+export const OMO_SESSION_PREFIX = "omo-";
+
+export function buildSessionReminderMessage(sessions: string[]): string {
+  if (sessions.length === 0) return "";
+  return `\n\n[System Reminder] Active omo-* tmux sessions: ${sessions.join(", ")}`;
+}
--- a/src/hooks/interactive-bash-session/index.ts
+++ b/src/hooks/interactive-bash-session/index.ts
@@ -0,0 +1,262 @@
+import type { PluginInput } from "@opencode-ai/plugin";
+import {
+  loadInteractiveBashSessionState,
+  saveInteractiveBashSessionState,
+  clearInteractiveBashSessionState,
+} from "./storage";
+import { OMO_SESSION_PREFIX, buildSessionReminderMessage } from "./constants";
+import type { InteractiveBashSessionState } from "./types";
+
+interface ToolExecuteInput {
+  tool: string;
+  sessionID: string;
+  callID: string;
+  args?: Record<string, unknown>;
+}
+
+interface ToolExecuteOutput {
+  title: string;
+  output: string;
+  metadata: unknown;
+}
+
+interface EventInput {
+  event: {
+    type: string;
+    properties?: unknown;
+  };
+}
+
+/**
+ * Quote-aware command tokenizer with escape handling
+ * Handles single/double quotes and backslash escapes
+ */
+function tokenizeCommand(cmd: string): string[] {
+  const tokens: string[] = []
+  let current = ""
+  let inQuote = false
+  let quoteChar = ""
+  let escaped = false
+
+  for (let i = 0; i < cmd.length; i++) {
+    const char = cmd[i]
+
+    if (escaped) {
+      current += char
+      escaped = false
+      continue
+    }
+
+    if (char === "\\") {
+      escaped = true
+      continue
+    }
+
+    if ((char === "'" || char === '"') && !inQuote) {
+      inQuote = true
+      quoteChar = char
+    } else if (char === quoteChar && inQuote) {
+      inQuote = false
+      quoteChar = ""
+    } else if (char === " " && !inQuote) {
+      if (current) {
+        tokens.push(current)
+        current = ""
+      }
+    } else {
+      current += char
+    }
+  }
+
+  if (current) tokens.push(current)
+  return tokens
+}
+
+/**
+ * Normalize session name by stripping :window and .pane suffixes
+ * e.g., "omo-x:1" -> "omo-x", "omo-x:1.2" -> "omo-x"
+ */
+function normalizeSessionName(name: string): string {
+  return name.split(":")[0].split(".")[0]
+}
+
+function findFlagValue(tokens: string[], flag: string): string | null {
+  for (let i = 0; i < tokens.length - 1; i++) {
+    if (tokens[i] === flag) return tokens[i + 1]
+  }
+  return null
+}
+
+/**
+ * Extract session name from tokens, considering the subCommand
+ * For new-session: prioritize -s over -t
+ * For other commands: use -t
+ */
+function extractSessionNameFromTokens(tokens: string[], subCommand: string): string | null {
+  if (subCommand === "new-session") {
+    const sFlag = findFlagValue(tokens, "-s")
+    if (sFlag) return normalizeSessionName(sFlag)
+    const tFlag = findFlagValue(tokens, "-t")
+    if (tFlag) return normalizeSessionName(tFlag)
+  } else {
+    const tFlag = findFlagValue(tokens, "-t")
+    if (tFlag) return normalizeSessionName(tFlag)
+  }
+  return null
+}
+
+/**
+ * Find the tmux subcommand from tokens, skipping global options.
+ * tmux allows global options before the subcommand:
+ * e.g., `tmux -L socket-name new-session -s omo-x`
+ * Global options with args: -L, -S, -f, -c, -T
+ * Standalone flags: -C, -v, -V, etc.
+ * Special: -- (end of options marker)
+ */
+function findSubcommand(tokens: string[]): string {
+  // Options that require an argument: -L, -S, -f, -c, -T
+  const globalOptionsWithArgs = new Set(["-L", "-S", "-f", "-c", "-T"])
+
+  let i = 0
+  while (i < tokens.length) {
+    const token = tokens[i]
+
+    // Handle end of options marker
+    if (token === "--") {
+      // Next token is the subcommand
+      return tokens[i + 1] ?? ""
+    }
+
+    if (globalOptionsWithArgs.has(token)) {
+      // Skip the option and its argument
+      i += 2
+      continue
+    }
+
+    if (token.startsWith("-")) {
+      // Skip standalone flags like -C, -v, -V
+      i++
+      continue
+    }
+
+    // Found the subcommand
+    return token
+  }
+
+  return ""
+}
+
+export function createInteractiveBashSessionHook(_ctx: PluginInput) {
+  const sessionStates = new Map<string, InteractiveBashSessionState>();
+
+  function getOrCreateState(sessionID: string): InteractiveBashSessionState {
+    if (!sessionStates.has(sessionID)) {
+      const persisted = loadInteractiveBashSessionState(sessionID);
+      const state: InteractiveBashSessionState = persisted ?? {
+        sessionID,
+        tmuxSessions: new Set<string>(),
+        updatedAt: Date.now(),
+      };
+      sessionStates.set(sessionID, state);
+    }
+    return sessionStates.get(sessionID)!;
+  }
+
+  function isOmoSession(sessionName: string | null): boolean {
+    return sessionName !== null && sessionName.startsWith(OMO_SESSION_PREFIX);
+  }
+
+  async function killAllTrackedSessions(
+    state: InteractiveBashSessionState,
+  ): Promise<void> {
+    for (const sessionName of state.tmuxSessions) {
+      try {
+        const proc = Bun.spawn(["tmux", "kill-session", "-t", sessionName], {
+          stdout: "ignore",
+          stderr: "ignore",
+        });
+        await proc.exited;
+      } catch {}
+    }
+  }
+
+  const toolExecuteAfter = async (
+    input: ToolExecuteInput,
+    output: ToolExecuteOutput,
+  ) => {
+    const { tool, sessionID, args } = input;
+    const toolLower = tool.toLowerCase();
+
+    if (toolLower !== "interactive_bash") {
+      return;
+    }
+
+    if (typeof args?.tmux_command !== "string") {
+      return;
+    }
+
+    const tmuxCommand = args.tmux_command;
+    const tokens = tokenizeCommand(tmuxCommand);
+    const subCommand = findSubcommand(tokens);
+    const state = getOrCreateState(sessionID);
+    let stateChanged = false;
+
+    const toolOutput = output?.output ?? ""
+    if (toolOutput.startsWith("Error:")) {
+      return
+    }
+
+    const isNewSession = subCommand === "new-session";
+    const isKillSession = subCommand === "kill-session";
+    const isKillServer = subCommand === "kill-server";
+
+    const sessionName = extractSessionNameFromTokens(tokens, subCommand);
+
+    if (isNewSession && isOmoSession(sessionName)) {
+      state.tmuxSessions.add(sessionName!);
+      stateChanged = true;
+    } else if (isKillSession && isOmoSession(sessionName)) {
+      state.tmuxSessions.delete(sessionName!);
+      stateChanged = true;
+    } else if (isKillServer) {
+      state.tmuxSessions.clear();
+      stateChanged = true;
+    }
+
+    if (stateChanged) {
+      state.updatedAt = Date.now();
+      saveInteractiveBashSessionState(state);
+    }
+
+    const isSessionOperation = isNewSession || isKillSession || isKillServer;
+    if (isSessionOperation) {
+      const reminder = buildSessionReminderMessage(
+        Array.from(state.tmuxSessions),
+      );
+      if (reminder) {
+        output.output += reminder;
+      }
+    }
+  };
+
+  const eventHandler = async ({ event }: EventInput) => {
+    const props = event.properties as Record<string, unknown> | undefined;
+
+    if (event.type === "session.deleted") {
+      const sessionInfo = props?.info as { id?: string } | undefined;
+      const sessionID = sessionInfo?.id;
+
+      if (sessionID) {
+        const state = getOrCreateState(sessionID);
+        await killAllTrackedSessions(state);
+        sessionStates.delete(sessionID);
+        clearInteractiveBashSessionState(sessionID);
+      }
+    }
+  };
+
+  return {
+    "tool.execute.after": toolExecuteAfter,
+    event: eventHandler,
+  };
+}
--- a/src/hooks/interactive-bash-session/storage.ts
+++ b/src/hooks/interactive-bash-session/storage.ts
@@ -0,0 +1,59 @@
+import {
+  existsSync,
+  mkdirSync,
+  readFileSync,
+  writeFileSync,
+  unlinkSync,
+} from "node:fs";
+import { join } from "node:path";
+import { INTERACTIVE_BASH_SESSION_STORAGE } from "./constants";
+import type {
+  InteractiveBashSessionState,
+  SerializedInteractiveBashSessionState,
+} from "./types";
+
+function getStoragePath(sessionID: string): string {
+  return join(INTERACTIVE_BASH_SESSION_STORAGE, `${sessionID}.json`);
+}
+
+export function loadInteractiveBashSessionState(
+  sessionID: string,
+): InteractiveBashSessionState | null {
+  const filePath = getStoragePath(sessionID);
+  if (!existsSync(filePath)) return null;
+
+  try {
+    const content = readFileSync(filePath, "utf-8");
+    const serialized = JSON.parse(content) as SerializedInteractiveBashSessionState;
+    return {
+      sessionID: serialized.sessionID,
+      tmuxSessions: new Set(serialized.tmuxSessions),
+      updatedAt: serialized.updatedAt,
+    };
+  } catch {
+    return null;
+  }
+}
+
+export function saveInteractiveBashSessionState(
+  state: InteractiveBashSessionState,
+): void {
+  if (!existsSync(INTERACTIVE_BASH_SESSION_STORAGE)) {
+    mkdirSync(INTERACTIVE_BASH_SESSION_STORAGE, { recursive: true });
+  }
+
+  const filePath = getStoragePath(state.sessionID);
+  const serialized: SerializedInteractiveBashSessionState = {
+    sessionID: state.sessionID,
+    tmuxSessions: Array.from(state.tmuxSessions),
+    updatedAt: state.updatedAt,
+  };
+  writeFileSync(filePath, JSON.stringify(serialized, null, 2));
+}
+
+export function clearInteractiveBashSessionState(sessionID: string): void {
+  const filePath = getStoragePath(sessionID);
+  if (existsSync(filePath)) {
+    unlinkSync(filePath);
+  }
+}
--- a/src/hooks/interactive-bash-session/types.ts
+++ b/src/hooks/interactive-bash-session/types.ts
@@ -0,0 +1,11 @@
+export interface InteractiveBashSessionState {
+  sessionID: string;
+  tmuxSessions: Set<string>;
+  updatedAt: number;
+}
+
+export interface SerializedInteractiveBashSessionState {
+  sessionID: string;
+  tmuxSessions: string[];
+  updatedAt: number;
+}
--- a/src/hooks/non-interactive-env/constants.ts
+++ b/src/hooks/non-interactive-env/constants.ts
@@ -0,0 +1,9 @@
+export const HOOK_NAME = "non-interactive-env"
+
+export const NON_INTERACTIVE_ENV: Record<string, string> = {
+  CI: "true",
+  DEBIAN_FRONTEND: "noninteractive",
+  GIT_TERMINAL_PROMPT: "0",
+  GCM_INTERACTIVE: "never",
+  HOMEBREW_NO_AUTO_UPDATE: "1",
+}
--- a/src/hooks/non-interactive-env/index.ts
+++ b/src/hooks/non-interactive-env/index.ts
@@ -0,0 +1,34 @@
+import type { PluginInput } from "@opencode-ai/plugin"
+import { HOOK_NAME, NON_INTERACTIVE_ENV } from "./constants"
+import { log } from "../../shared"
+
+export * from "./constants"
+export * from "./types"
+
+export function createNonInteractiveEnvHook(_ctx: PluginInput) {
+  return {
+    "tool.execute.before": async (
+      input: { tool: string; sessionID: string; callID: string },
+      output: { args: Record<string, unknown> }
+    ): Promise<void> => {
+      if (input.tool.toLowerCase() !== "bash") {
+        return
+      }
+
+      const command = output.args.command as string | undefined
+      if (!command) {
+        return
+      }
+
+      output.args.env = {
+        ...(output.args.env as Record<string, string> | undefined),
+        ...NON_INTERACTIVE_ENV,
+      }
+
+      log(`[${HOOK_NAME}] Set non-interactive environment variables`, {
+        sessionID: input.sessionID,
+        env: NON_INTERACTIVE_ENV,
+      })
+    },
+  }
+}
--- a/src/hooks/non-interactive-env/types.ts
+++ b/src/hooks/non-interactive-env/types.ts
@@ -0,0 +1,3 @@
+export interface NonInteractiveEnvConfig {
+  disabled?: boolean
+}
--- a/src/hooks/session-notification.ts
+++ b/src/hooks/session-notification.ts
@@ -48,19 +48,34 @@ async function sendNotification(
  title: string,
  message: string
 ): Promise<void> {
-  const escapedTitle = title.replace(/"/g, '\\"').replace(/'/g, "\\'")
-  const escapedMessage = message.replace(/"/g, '\\"').replace(/'/g, "\\'")
-
  switch (p) {
-    case "darwin":
-      await ctx.$`osascript -e ${"display notification \"" + escapedMessage + "\" with title \"" + escapedTitle + "\""}`
+    case "darwin": {
+      const esTitle = title.replace(/\\/g, "\\\\").replace(/"/g, '\\"')
+      const esMessage = message.replace(/\\/g, "\\\\").replace(/"/g, '\\"')
+      await ctx.$`osascript -e ${"display notification \"" + esMessage + "\" with title \"" + esTitle + "\""}`
      break
+    }
    case "linux":
-      await ctx.$`notify-send ${escapedTitle} ${escapedMessage}`.catch(() => {})
+      await ctx.$`notify-send ${title} ${message} 2>/dev/null`.catch(() => {})
      break
-    case "win32":
-      await ctx.$`powershell -Command ${"[System.Reflection.Assembly]::LoadWithPartialName('System.Windows.Forms'); [System.Windows.Forms.MessageBox]::Show('" + escapedMessage + "', '" + escapedTitle + "')"}`
+    case "win32": {
+      const psTitle = title.replace(/'/g, "''")
+      const psMessage = message.replace(/'/g, "''")
+      const toastScript = `
+[Windows.UI.Notifications.ToastNotificationManager, Windows.UI.Notifications, ContentType = WindowsRuntime] | Out-Null
+$Template = [Windows.UI.Notifications.ToastNotificationManager]::GetTemplateContent([Windows.UI.Notifications.ToastTemplateType]::ToastText02)
+$RawXml = [xml] $Template.GetXml()
+($RawXml.toast.visual.binding.text | Where-Object {$_.id -eq '1'}).AppendChild($RawXml.CreateTextNode('${psTitle}')) | Out-Null
+($RawXml.toast.visual.binding.text | Where-Object {$_.id -eq '2'}).AppendChild($RawXml.CreateTextNode('${psMessage}')) | Out-Null
+$SerializedXml = New-Object Windows.Data.Xml.Dom.XmlDocument
+$SerializedXml.LoadXml($RawXml.OuterXml)
+$Toast = [Windows.UI.Notifications.ToastNotification]::new($SerializedXml)
+$Notifier = [Windows.UI.Notifications.ToastNotificationManager]::CreateToastNotifier('OpenCode')
+$Notifier.Show($Toast)
+`.trim().replace(/\n/g, "; ")
+      await ctx.$`powershell -Command ${toastScript}`.catch(() => {})
      break
+    }
  }
 }

@@ -70,8 +85,8 @@ async function playSound(ctx: PluginInput, p: Platform, soundPath: string): Prom
      ctx.$`afplay ${soundPath}`.catch(() => {})
      break
    case "linux":
-      ctx.$`paplay ${soundPath}`.catch(() => {
-        ctx.$`aplay ${soundPath}`.catch(() => {})
+      ctx.$`paplay ${soundPath} 2>/dev/null`.catch(() => {
+        ctx.$`aplay ${soundPath} 2>/dev/null`.catch(() => {})
      })
      break
    case "win32":
--- a/src/hooks/session-recovery/index.ts
+++ b/src/hooks/session-recovery/index.ts
@@ -6,8 +6,10 @@ import {
  findMessageByIndexNeedingThinking,
  findMessagesWithOrphanThinking,
  findMessagesWithThinkingBlocks,
+  findMessagesWithThinkingOnly,
  injectTextPart,
  prependThinkingPart,
+  readParts,
  stripThinkingParts,
 } from "./storage"
 import type { MessageData } from "./types"
@@ -48,12 +50,29 @@ interface MessagePart {
 function getErrorMessage(error: unknown): string {
  if (!error) return ""
  if (typeof error === "string") return error.toLowerCase()
-  const errorObj = error as {
-    data?: { message?: string }
-    message?: string
-    error?: { message?: string }
+
+  const errorObj = error as Record<string, unknown>
+  const paths = [
+    errorObj.data,
+    errorObj.error,
+    errorObj,
+    (errorObj.data as Record<string, unknown>)?.error,
+  ]
+
+  for (const obj of paths) {
+    if (obj && typeof obj === "object") {
+      const msg = (obj as Record<string, unknown>).message
+      if (typeof msg === "string" && msg.length > 0) {
+        return msg.toLowerCase()
+      }
+    }
+  }
+
+  try {
+    return JSON.stringify(error).toLowerCase()
+  } catch {
+    return ""
  }
-  return (errorObj.data?.message || errorObj.error?.message || errorObj.message || "").toLowerCase()
 }

 function extractMessageIndex(error: unknown): number | null {
@@ -83,7 +102,12 @@ function detectErrorType(error: unknown): RecoveryErrorType {
    return "thinking_disabled_violation"
  }

-  if (message.includes("non-empty content") || message.includes("must have non-empty content")) {
+  if (
+    message.includes("non-empty content") ||
+    message.includes("must have non-empty content") ||
+    (message.includes("content") && message.includes("is empty")) ||
+    (message.includes("content field") && message.includes("empty"))
+  ) {
    return "empty_content_message"
  }

@@ -99,7 +123,17 @@ async function recoverToolResultMissing(
  sessionID: string,
  failedAssistantMsg: MessageData
 ): Promise<boolean> {
-  const parts = failedAssistantMsg.parts || []
+  // Try API parts first, fallback to filesystem if empty
+  let parts = failedAssistantMsg.parts || []
+  if (parts.length === 0 && failedAssistantMsg.info?.id) {
+    const storedParts = readParts(failedAssistantMsg.info.id)
+    parts = storedParts.map((p) => ({
+      type: p.type === "tool" ? "tool_use" : p.type,
+      id: "callID" in p ? (p as { callID?: string }).callID : p.id,
+      name: "tool" in p ? (p as { tool?: string }).tool : undefined,
+      input: "state" in p ? (p as { state?: { input?: Record<string, unknown> } }).state?.input : undefined,
+    }))
+  }
  const toolUseIds = extractToolUseIds(parts)

  if (toolUseIds.length === 0) {
@@ -177,6 +211,8 @@ async function recoverThinkingDisabledViolation(
  return anySuccess
 }

+const PLACEHOLDER_TEXT = "[user interrupted]"
+
 async function recoverEmptyContentMessage(
  _client: Client,
  sessionID: string,
@@ -187,23 +223,28 @@ async function recoverEmptyContentMessage(
  const targetIndex = extractMessageIndex(error)
  const failedID = failedAssistantMsg.info?.id

+  const thinkingOnlyIDs = findMessagesWithThinkingOnly(sessionID)
+  for (const messageID of thinkingOnlyIDs) {
+    injectTextPart(sessionID, messageID, PLACEHOLDER_TEXT)
+  }
+
  if (targetIndex !== null) {
    const targetMessageID = findEmptyMessageByIndex(sessionID, targetIndex)
    if (targetMessageID) {
-      return injectTextPart(sessionID, targetMessageID, "(interrupted)")
+      return injectTextPart(sessionID, targetMessageID, PLACEHOLDER_TEXT)
    }
  }

  if (failedID) {
-    if (injectTextPart(sessionID, failedID, "(interrupted)")) {
+    if (injectTextPart(sessionID, failedID, PLACEHOLDER_TEXT)) {
      return true
    }
  }

  const emptyMessageIDs = findEmptyMessages(sessionID)
-  let anySuccess = false
+  let anySuccess = thinkingOnlyIDs.length > 0
  for (const messageID of emptyMessageIDs) {
-    if (injectTextPart(sessionID, messageID, "(interrupted)")) {
+    if (injectTextPart(sessionID, messageID, PLACEHOLDER_TEXT)) {
      anySuccess = true
    }
  }
--- a/src/hooks/session-recovery/storage.ts
+++ b/src/hooks/session-recovery/storage.ts
@@ -133,20 +133,15 @@ export function findEmptyMessages(sessionID: string): string[] {

 export function findEmptyMessageByIndex(sessionID: string, targetIndex: number): string | null {
  const messages = readMessages(sessionID)
-  
-  // Try multiple indices to handle system message offset
-  // API includes system message at index 0, storage may not
-  const indicesToTry = [targetIndex, targetIndex - 1]
-  
+
+  // API index may differ from storage index due to system messages
+  const indicesToTry = [targetIndex, targetIndex - 1, targetIndex - 2]
+
  for (const idx of indicesToTry) {
    if (idx < 0 || idx >= messages.length) continue

    const targetMsg = messages[idx]
-    
-    // NOTE: Do NOT skip last assistant message here
-    // If API returned an error, this message is NOT the final assistant message
-    // (the API only allows empty content for the ACTUAL final assistant message)
-    
+
    if (!messageHasContent(targetMsg.id)) {
      return targetMsg.id
    }
@@ -177,6 +172,28 @@ export function findMessagesWithThinkingBlocks(sessionID: string): string[] {
  return result
 }

+export function findMessagesWithThinkingOnly(sessionID: string): string[] {
+  const messages = readMessages(sessionID)
+  const result: string[] = []
+
+  for (const msg of messages) {
+    if (msg.role !== "assistant") continue
+
+    const parts = readParts(msg.id)
+    if (parts.length === 0) continue
+
+    const hasThinking = parts.some((p) => THINKING_TYPES.has(p.type))
+    const hasTextContent = parts.some(hasContent)
+
+    // Has thinking but no text content = orphan thinking
+    if (hasThinking && !hasTextContent) {
+      result.push(msg.id)
+    }
+  }
+
+  return result
+}
+
 export function findMessagesWithOrphanThinking(sessionID: string): string[] {
  const messages = readMessages(sessionID)
  const result: string[] = []
--- a/src/hooks/todo-continuation-enforcer.ts
+++ b/src/hooks/todo-continuation-enforcer.ts
@@ -1,4 +1,13 @@
+import { existsSync, readdirSync } from "node:fs"
+import { join } from "node:path"
 import type { PluginInput } from "@opencode-ai/plugin"
+import {
+  findNearestMessageWithFields,
+  MESSAGE_STORAGE,
+} from "../features/hook-message-injector"
+import { log } from "../shared/logger"
+
+const HOOK_NAME = "todo-continuation-enforcer"

 export interface TodoContinuationEnforcer {
  handler: (input: { event: { type: string; properties?: unknown } }) => Promise<void>
@@ -21,6 +30,20 @@ Incomplete tasks remain in your todo list. Continue working on the next pending
 - Mark each task complete when finished
 - Do not stop until all tasks are done`

+function getMessageDir(sessionID: string): string | null {
+  if (!existsSync(MESSAGE_STORAGE)) return null
+
+  const directPath = join(MESSAGE_STORAGE, sessionID)
+  if (existsSync(directPath)) return directPath
+
+  for (const dir of readdirSync(MESSAGE_STORAGE)) {
+    const sessionPath = join(MESSAGE_STORAGE, dir, sessionID)
+    if (existsSync(sessionPath)) return sessionPath
+  }
+
+  return null
+}
+
 function detectInterrupt(error: unknown): boolean {
  if (!error) return false
  if (typeof error === "object") {
@@ -59,10 +82,12 @@ export function createTodoContinuationEnforcer(ctx: PluginInput): TodoContinuati
    if (event.type === "session.error") {
      const sessionID = props?.sessionID as string | undefined
      if (sessionID) {
+        const isInterrupt = detectInterrupt(props?.error)
        errorSessions.add(sessionID)
-        if (detectInterrupt(props?.error)) {
+        if (isInterrupt) {
          interruptedSessions.add(sessionID)
        }
+        log(`[${HOOK_NAME}] session.error received`, { sessionID, isInterrupt, error: props?.error })
        
        // Cancel pending continuation if error occurs
        const timer = pendingTimers.get(sessionID)
@@ -78,18 +103,23 @@ export function createTodoContinuationEnforcer(ctx: PluginInput): TodoContinuati
      const sessionID = props?.sessionID as string | undefined
      if (!sessionID) return

+      log(`[${HOOK_NAME}] session.idle received`, { sessionID })
+
      // Cancel any existing timer to debounce
      const existingTimer = pendingTimers.get(sessionID)
      if (existingTimer) {
        clearTimeout(existingTimer)
+        log(`[${HOOK_NAME}] Cancelled existing timer`, { sessionID })
      }

      // Schedule continuation check
      const timer = setTimeout(async () => {
        pendingTimers.delete(sessionID)
+        log(`[${HOOK_NAME}] Timer fired, checking conditions`, { sessionID })

        // Check if session is in recovery mode - if so, skip entirely without clearing state
        if (recoveringSessions.has(sessionID)) {
+          log(`[${HOOK_NAME}] Skipped: session in recovery mode`, { sessionID })
          return
        }

@@ -99,24 +129,30 @@ export function createTodoContinuationEnforcer(ctx: PluginInput): TodoContinuati
        errorSessions.delete(sessionID)

        if (shouldBypass) {
+          log(`[${HOOK_NAME}] Skipped: error/interrupt bypass`, { sessionID })
          return
        }

        if (remindedSessions.has(sessionID)) {
+          log(`[${HOOK_NAME}] Skipped: already reminded this session`, { sessionID })
          return
        }

        let todos: Todo[] = []
        try {
+          log(`[${HOOK_NAME}] Fetching todos for session`, { sessionID })
          const response = await ctx.client.session.todo({
            path: { id: sessionID },
          })
          todos = (response.data ?? response) as Todo[]
-        } catch {
+          log(`[${HOOK_NAME}] Todo API response`, { sessionID, todosCount: todos?.length ?? 0 })
+        } catch (err) {
+          log(`[${HOOK_NAME}] Todo API error`, { sessionID, error: String(err) })
          return
        }

        if (!todos || todos.length === 0) {
+          log(`[${HOOK_NAME}] No todos found`, { sessionID })
          return
        }

@@ -125,21 +161,30 @@ export function createTodoContinuationEnforcer(ctx: PluginInput): TodoContinuati
        )

        if (incomplete.length === 0) {
+          log(`[${HOOK_NAME}] All todos completed`, { sessionID, total: todos.length })
          return
        }

+        log(`[${HOOK_NAME}] Found incomplete todos`, { sessionID, incomplete: incomplete.length, total: todos.length })
        remindedSessions.add(sessionID)

        // Re-check if abort occurred during the delay/fetch
        if (interruptedSessions.has(sessionID) || errorSessions.has(sessionID) || recoveringSessions.has(sessionID)) {
+          log(`[${HOOK_NAME}] Abort occurred during delay/fetch`, { sessionID })
          remindedSessions.delete(sessionID)
          return
        }

        try {
+          // Get previous message's agent info to respect agent mode
+          const messageDir = getMessageDir(sessionID)
+          const prevMessage = messageDir ? findNearestMessageWithFields(messageDir) : null
+
+          log(`[${HOOK_NAME}] Injecting continuation prompt`, { sessionID, agent: prevMessage?.agent })
          await ctx.client.session.prompt({
            path: { id: sessionID },
            body: {
+              agent: prevMessage?.agent,
              parts: [
                {
                  type: "text",
@@ -149,7 +194,9 @@ export function createTodoContinuationEnforcer(ctx: PluginInput): TodoContinuati
            },
            query: { directory: ctx.directory },
          })
-        } catch {
+          log(`[${HOOK_NAME}] Continuation prompt injected successfully`, { sessionID })
+        } catch (err) {
+          log(`[${HOOK_NAME}] Prompt injection failed`, { sessionID, error: String(err) })
          remindedSessions.delete(sessionID)
        }
      }, 200)
@@ -160,16 +207,23 @@ export function createTodoContinuationEnforcer(ctx: PluginInput): TodoContinuati
    if (event.type === "message.updated") {
      const info = props?.info as Record<string, unknown> | undefined
      const sessionID = info?.sessionID as string | undefined
+      log(`[${HOOK_NAME}] message.updated received`, { sessionID, role: info?.role })
+      
      if (sessionID && info?.role === "user") {
-        remindedSessions.delete(sessionID)
-        
-        // Cancel pending continuation on user interaction
+        // Cancel pending continuation on user interaction (real user input)
        const timer = pendingTimers.get(sessionID)
        if (timer) {
          clearTimeout(timer)
          pendingTimers.delete(sessionID)
+          log(`[${HOOK_NAME}] Cancelled pending timer on user message`, { sessionID })
        }
      }
+      
+      // Clear reminded state when assistant responds (allows re-remind on next idle)
+      if (sessionID && info?.role === "assistant" && remindedSessions.has(sessionID)) {
+        remindedSessions.delete(sessionID)
+        log(`[${HOOK_NAME}] Cleared remindedSessions on assistant response`, { sessionID })
+      }
    }

    if (event.type === "session.deleted") {
--- a/src/hooks/tool-output-truncator.ts
+++ b/src/hooks/tool-output-truncator.ts
@@ -1,9 +1,10 @@
 import type { PluginInput } from "@opencode-ai/plugin"
 import { createDynamicTruncator } from "../shared/dynamic-truncator"

+// Note: "grep" and "Grep" are handled by dedicated grep-output-truncator.ts
 const TRUNCATABLE_TOOLS = [
-  "Grep",
  "safe_grep",
+  "glob",
  "Glob",
  "safe_glob",
  "lsp_find_references",
@@ -11,6 +12,8 @@ const TRUNCATABLE_TOOLS = [
  "lsp_workspace_symbols",
  "lsp_diagnostics",
  "ast_grep_search",
+  "interactive_bash",
+  "Interactive_bash",
 ]

 export function createToolOutputTruncatorHook(ctx: PluginInput) {
--- a/src/index.ts
+++ b/src/index.ts
@@ -18,6 +18,8 @@ import {
  createAutoUpdateCheckerHook,
  createKeywordDetectorHook,
  createAgentUsageReminderHook,
+  createNonInteractiveEnvHook,
+  createInteractiveBashSessionHook,
 } from "./hooks";
 import { createGoogleAntigravityAuthPlugin } from "./auth/antigravity";
 import {
@@ -42,7 +44,7 @@ import {
  getCurrentSessionTitle,
 } from "./features/claude-code-session-state";
 import { updateTerminalTitle } from "./features/terminal";
-import { builtinTools, createCallOmoAgent, createBackgroundTools, createLookAt } from "./tools";
+import { builtinTools, createCallOmoAgent, createBackgroundTools, createLookAt, interactive_bash, getTmuxPath } from "./tools";
 import { BackgroundManager } from "./features/background-agent";
 import { createBuiltinMcps } from "./mcp";
 import { OhMyOpenCodeConfigSchema, type OhMyOpenCodeConfig, type HookName } from "./config";
@@ -238,6 +240,12 @@ const OhMyOpenCodePlugin: Plugin = async (ctx) => {
  const agentUsageReminder = isHookEnabled("agent-usage-reminder")
    ? createAgentUsageReminderHook(ctx)
    : null;
+  const nonInteractiveEnv = isHookEnabled("non-interactive-env")
+    ? createNonInteractiveEnvHook(ctx)
+    : null;
+  const interactiveBashSession = isHookEnabled("interactive-bash-session")
+    ? createInteractiveBashSessionHook(ctx)
+    : null;

  updateTerminalTitle({ sessionId: "main" });

@@ -255,6 +263,8 @@ const OhMyOpenCodePlugin: Plugin = async (ctx) => {
    ? await createGoogleAntigravityAuthPlugin(ctx)
    : null;

+  const tmuxAvailable = await getTmuxPath();
+
  return {
    ...(googleAuthHooks ? { auth: googleAuthHooks.auth } : {}),

@@ -263,6 +273,7 @@ const OhMyOpenCodePlugin: Plugin = async (ctx) => {
      ...backgroundTools,
      call_omo_agent: callOmoAgent,
      look_at: lookAt,
+      ...(tmuxAvailable ? { interactive_bash } : {}),
    },

    "chat.message": async (input, output) => {
@@ -274,6 +285,7 @@ const OhMyOpenCodePlugin: Plugin = async (ctx) => {
      const builtinAgents = createBuiltinAgents(
        pluginConfig.disabled_agents,
        pluginConfig.agents,
+        ctx.directory,
      );

      const userAgents = (pluginConfig.claude_code?.agents ?? true) ? loadUserAgents() : {};
@@ -382,6 +394,7 @@ const OhMyOpenCodePlugin: Plugin = async (ctx) => {
      await anthropicAutoCompact?.event(input);
      await keywordDetector?.event(input);
      await agentUsageReminder?.event(input);
+      await interactiveBashSession?.event(input);

      const { event } = input;
      const props = event.properties as Record<string, unknown> | undefined;
@@ -479,8 +492,21 @@ const OhMyOpenCodePlugin: Plugin = async (ctx) => {

    "tool.execute.before": async (input, output) => {
      await claudeCodeHooks["tool.execute.before"](input, output);
+      await nonInteractiveEnv?.["tool.execute.before"](input, output);
      await commentChecker?.["tool.execute.before"](input, output);

+      if (input.tool === "task") {
+        const args = output.args as Record<string, unknown>;
+        const subagentType = args.subagent_type as string;
+        const isExploreOrLibrarian = ["explore", "librarian"].includes(subagentType);
+
+        args.tools = {
+          ...(args.tools as Record<string, boolean> | undefined),
+          background_task: false,
+          ...(isExploreOrLibrarian ? { call_omo_agent: false } : {}),
+        };
+      }
+
      if (input.sessionID === getMainSessionID()) {
        updateTerminalTitle({
          sessionId: input.sessionID,
@@ -502,6 +528,7 @@ const OhMyOpenCodePlugin: Plugin = async (ctx) => {
      await rulesInjector?.["tool.execute.after"](input, output);
      await emptyTaskResponseDetector?.["tool.execute.after"](input, output);
      await agentUsageReminder?.["tool.execute.after"](input, output);
+      await interactiveBashSession?.["tool.execute.after"](input, output);

      if (input.sessionID === getMainSessionID()) {
        updateTerminalTitle({
--- a/src/shared/command-executor.ts
+++ b/src/shared/command-executor.ts
@@ -2,9 +2,14 @@ import { spawn } from "child_process"
 import { exec } from "child_process"
 import { promisify } from "util"
 import { existsSync } from "fs"
+import { homedir } from "os"

 const DEFAULT_ZSH_PATHS = ["/bin/zsh", "/usr/bin/zsh", "/usr/local/bin/zsh"]

+function getHomeDir(): string {
+  return process.env.HOME || process.env.USERPROFILE || homedir()
+}
+
 function findZshPath(customZshPath?: string): string | null {
  if (customZshPath && existsSync(customZshPath)) {
    return customZshPath
@@ -39,7 +44,7 @@ export async function executeHookCommand(
  cwd: string,
  options?: ExecuteHookOptions
 ): Promise<CommandResult> {
-  const home = process.env.HOME ?? ""
+  const home = getHomeDir()

  let expandedCommand = command
    .replace(/^~(?=\/|$)/g, home)
--- a/src/tools/background-task/constants.ts
+++ b/src/tools/background-task/constants.ts
@@ -9,9 +9,11 @@ Use this for:

 Arguments:
 - description: Short task description (shown in status)
- prompt: Full detailed prompt for the agent
+- prompt: Full detailed prompt for the agent (MUST be in English for optimal LLM performance)
 - agent: Agent type to use (any agent allowed)

+IMPORTANT: Always write prompts in English regardless of user's language. LLMs perform significantly better with English prompts.
+
 Returns immediately with task ID and session info. Use \`background_output\` to check progress or retrieve results.`

 export const BACKGROUND_OUTPUT_DESCRIPTION = `Get output from a background task.
@@ -21,17 +23,7 @@ Arguments:
 - block: If true, wait for task completion. If false (default), return current status immediately.
 - timeout: Max wait time in ms when blocking (default: 60000, max: 600000)

-Returns:
- When not blocking: Returns current status with task ID, description, agent, status, duration, and progress info
- When blocking: Waits for completion, then returns full result
-
-IMPORTANT: The system automatically notifies the main session when background tasks complete.
-You typically don't need block=true - just use block=false to check status, and the system will notify you when done.
-
-Use this to:
- Check task progress (block=false) - returns full status info, NOT empty
- Wait for and retrieve task result (block=true) - only when you explicitly need to wait
- Set custom timeout for long tasks`
+The system automatically notifies when background tasks complete. You typically don't need block=true.`

 export const BACKGROUND_CANCEL_DESCRIPTION = `Cancel a running background task.

--- a/src/tools/call-omo-agent/constants.ts
+++ b/src/tools/call-omo-agent/constants.ts
@@ -21,4 +21,5 @@ Usage notes:
 3. Each agent invocation is stateless unless you provide a session_id
 4. Your prompt should contain a highly detailed task description for the agent to perform autonomously
 5. Clearly tell the agent whether you expect it to write code or just to do research
-6. For long-running research tasks, use run_in_background=true to avoid blocking`
+6. For long-running research tasks, use run_in_background=true to avoid blocking
+7. **IMPORTANT**: Always write prompts in English regardless of user's language. LLMs perform significantly better with English prompts.`
--- a/src/tools/index.ts
+++ b/src/tools/index.ts
@@ -22,6 +22,9 @@ import { glob } from "./glob"
 import { slashcommand } from "./slashcommand"
 import { skill } from "./skill"

+export { interactive_bash, startBackgroundCheck as startTmuxCheck } from "./interactive-bash"
+export { getTmuxPath } from "./interactive-bash/utils"
+
 import {
  createBackgroundTask,
  createBackgroundOutput,
--- a/src/tools/interactive-bash/constants.ts
+++ b/src/tools/interactive-bash/constants.ts
@@ -0,0 +1,22 @@
+export const DEFAULT_TIMEOUT_MS = 60_000
+
+export const BLOCKED_TMUX_SUBCOMMANDS = [
+  "capture-pane",
+  "capturep",
+  "save-buffer",
+  "saveb",
+  "show-buffer",
+  "showb",
+  "pipe-pane",
+  "pipep",
+]
+
+export const INTERACTIVE_BASH_DESCRIPTION = `Execute tmux commands for interactive terminal session management.
+
+Use session names following the pattern "omo-{name}" for automatic tracking.
+
+BLOCKED COMMANDS (use bash tool instead):
+- capture-pane / capturep: Use bash to read output files or pipe output
+- save-buffer / saveb: Use bash to save content to files
+- show-buffer / showb: Use bash to read buffer content
+- pipe-pane / pipep: Use bash for piping output`
--- a/src/tools/interactive-bash/index.ts
+++ b/src/tools/interactive-bash/index.ts
@@ -0,0 +1,4 @@
+import { interactive_bash } from "./tools"
+import { startBackgroundCheck } from "./utils"
+
+export { interactive_bash, startBackgroundCheck }
--- a/src/tools/interactive-bash/tools.ts
+++ b/src/tools/interactive-bash/tools.ts
@@ -0,0 +1,104 @@
+import { tool } from "@opencode-ai/plugin/tool"
+import { BLOCKED_TMUX_SUBCOMMANDS, DEFAULT_TIMEOUT_MS, INTERACTIVE_BASH_DESCRIPTION } from "./constants"
+import { getCachedTmuxPath } from "./utils"
+
+/**
+ * Quote-aware command tokenizer with escape handling
+ * Handles single/double quotes and backslash escapes without external dependencies
+ */
+export function tokenizeCommand(cmd: string): string[] {
+  const tokens: string[] = []
+  let current = ""
+  let inQuote = false
+  let quoteChar = ""
+  let escaped = false
+
+  for (let i = 0; i < cmd.length; i++) {
+    const char = cmd[i]
+
+    if (escaped) {
+      current += char
+      escaped = false
+      continue
+    }
+
+    if (char === "\\") {
+      escaped = true
+      continue
+    }
+
+    if ((char === "'" || char === '"') && !inQuote) {
+      inQuote = true
+      quoteChar = char
+    } else if (char === quoteChar && inQuote) {
+      inQuote = false
+      quoteChar = ""
+    } else if (char === " " && !inQuote) {
+      if (current) {
+        tokens.push(current)
+        current = ""
+      }
+    } else {
+      current += char
+    }
+  }
+
+  if (current) tokens.push(current)
+  return tokens
+}
+
+export const interactive_bash = tool({
+  description: INTERACTIVE_BASH_DESCRIPTION,
+  args: {
+    tmux_command: tool.schema.string().describe("The tmux command to execute (without 'tmux' prefix)"),
+  },
+  execute: async (args) => {
+    try {
+      const tmuxPath = getCachedTmuxPath() ?? "tmux"
+
+      const parts = tokenizeCommand(args.tmux_command)
+
+      if (parts.length === 0) {
+        return "Error: Empty tmux command"
+      }
+
+      const subcommand = parts[0].toLowerCase()
+      if (BLOCKED_TMUX_SUBCOMMANDS.includes(subcommand)) {
+        return `Error: '${parts[0]}' is blocked. Use bash tool instead for capturing/printing terminal output.`
+      }
+
+      const proc = Bun.spawn([tmuxPath, ...parts], {
+        stdout: "pipe",
+        stderr: "pipe",
+      })
+
+      const timeoutPromise = new Promise<never>((_, reject) => {
+        const id = setTimeout(() => {
+          proc.kill()
+          reject(new Error(`Timeout after ${DEFAULT_TIMEOUT_MS}ms`))
+        }, DEFAULT_TIMEOUT_MS)
+        proc.exited.then(() => clearTimeout(id))
+      })
+
+      // Read stdout and stderr in parallel to avoid race conditions
+      const [stdout, stderr, exitCode] = await Promise.race([
+        Promise.all([
+          new Response(proc.stdout).text(),
+          new Response(proc.stderr).text(),
+          proc.exited,
+        ]),
+        timeoutPromise,
+      ])
+
+      // Check exitCode properly - return error even if stderr is empty
+      if (exitCode !== 0) {
+        const errorMsg = stderr.trim() || `Command failed with exit code ${exitCode}`
+        return `Error: ${errorMsg}`
+      }
+
+      return stdout || "(no output)"
+    } catch (e) {
+      return `Error: ${e instanceof Error ? e.message : String(e)}`
+    }
+  },
+})
--- a/src/tools/interactive-bash/types.ts
+++ b/src/tools/interactive-bash/types.ts
@@ -0,0 +1,3 @@
+export interface InteractiveBashArgs {
+  tmux_command: string
+}
--- a/src/tools/interactive-bash/utils.ts
+++ b/src/tools/interactive-bash/utils.ts
@@ -0,0 +1,71 @@
+import { spawn } from "bun"
+
+let tmuxPath: string | null = null
+let initPromise: Promise<string | null> | null = null
+
+async function findTmuxPath(): Promise<string | null> {
+  const isWindows = process.platform === "win32"
+  const cmd = isWindows ? "where" : "which"
+
+  try {
+    const proc = spawn([cmd, "tmux"], {
+      stdout: "pipe",
+      stderr: "pipe",
+    })
+
+    const exitCode = await proc.exited
+    if (exitCode !== 0) {
+      return null
+    }
+
+    const stdout = await new Response(proc.stdout).text()
+    const path = stdout.trim().split("\n")[0]
+
+    if (!path) {
+      return null
+    }
+
+    const verifyProc = spawn([path, "-V"], {
+      stdout: "pipe",
+      stderr: "pipe",
+    })
+
+    const verifyExitCode = await verifyProc.exited
+    if (verifyExitCode !== 0) {
+      return null
+    }
+
+    return path
+  } catch {
+    return null
+  }
+}
+
+export async function getTmuxPath(): Promise<string | null> {
+  if (tmuxPath !== null) {
+    return tmuxPath
+  }
+
+  if (initPromise) {
+    return initPromise
+  }
+
+  initPromise = (async () => {
+    const path = await findTmuxPath()
+    tmuxPath = path
+    return path
+  })()
+
+  return initPromise
+}
+
+export function getCachedTmuxPath(): string | null {
+  return tmuxPath
+}
+
+export function startBackgroundCheck(): void {
+  if (!initPromise) {
+    initPromise = getTmuxPath()
+    initPromise.catch(() => {})
+  }
+}
--- a/src/tools/look-at/constants.ts
+++ b/src/tools/look-at/constants.ts
@@ -2,22 +2,9 @@ export const MULTIMODAL_LOOKER_AGENT = "multimodal-looker" as const

 export const LOOK_AT_DESCRIPTION = `Analyze media files (PDFs, images, diagrams) that require visual interpretation.

-Use this tool to extract specific information from files that cannot be processed as plain text:
- PDF documents: extract text, tables, structure, specific sections
- Images: describe layouts, UI elements, text content, diagrams
- Charts/Graphs: explain data, trends, relationships
- Screenshots: identify UI components, text, visual elements
- Architecture diagrams: explain flows, connections, components
-
 Parameters:
 - file_path: Absolute path to the file to analyze
 - goal: What specific information to extract (be specific for better results)

-Examples:
- "Extract all API endpoints from this OpenAPI spec PDF"
- "Describe the UI layout and components in this screenshot"
- "Explain the data flow in this architecture diagram"
- "List all table data from page 3 of this PDF"
-
 This tool uses a separate context window with Gemini 2.5 Flash for multimodal analysis,
 saving tokens in the main conversation while providing accurate visual interpretation.`
Author	SHA1	Message	Date
github-actions[bot]	89e9fd2083	release: v2.1.2	2025-12-15 23:58:46 +00:00
Junho Yeo	da63b09064	fix(session-notification): Replace blocking MessageBox with native toast on Windows (#62 ) The previous Windows implementation used System.Windows.Forms.MessageBox which displays a blocking modal dialog requiring user interaction. This replaces it with the native Windows.UI.Notifications.ToastNotificationManager API (Windows 10+) which shows a non-intrusive toast notification in the corner, consistent with macOS and Linux behavior. - Uses native Toast API (no external dependencies like BurntToast) - Non-blocking: notification auto-dismisses - Graceful degradation: silently fails on older Windows versions - Fix escaping for each platform (PowerShell: '' for quotes, AppleScript: backslash)	2025-12-16 08:54:55 +09:00
github-actions[bot]	aafee74688	release: v2.1.1	2025-12-15 16:22:13 +00:00
YeonGyu-Kim	be900454d8	fix: Improve Windows compatibility for paths and shell config - Use os.tmpdir() instead of hardcoded /tmp for cross-platform temp files - Use os.homedir() with USERPROFILE fallback for Windows home directory - Disable forceZsh on Windows (zsh not available by default) 🤖 GENERATED WITH ASSISTANCE OF [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)	2025-12-16 01:02:49 +09:00
YeonGyu-Kim	a10ee64c51	fix(agents): Use exclude pattern for tools config to enable MCP tools Changed agent tools configuration from include pattern (listing allowed tools) to exclude pattern (listing disabled tools only). This ensures MCP tools like websearch_exa, context7, and grep_app are available to agents by default. Affected agents: librarian, oracle, explore, multimodal-looker 🤖 GENERATED WITH ASSISTANCE OF [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)	2025-12-16 01:02:39 +09:00
YeonGyu-Kim	116a90db6a	enhance(background-agent): Prevent recursive tool calls and wait for session todos before completion - Remove call_omo_agent from blocked tools (only calls explore/librarian, safe) - Keep task and background_task blocked to prevent recursion - Add checkSessionTodos() to verify incomplete todos before marking tasks complete - Update session.idle event handler to respect todo status - Add polling check in task completion to wait for todo-continuation 🤖 Generated with assistance of OhMyOpenCode (https://github.com/code-yeongyu/oh-my-opencode)	2025-12-15 23:54:59 +09:00
YeonGyu-Kim	060e58e423	Update AGENTS.md	2025-12-15 23:46:06 +09:00
YeonGyu-Kim	780bb3780a	docs: Add Japanese README translation and update language selector links - Create README.ja.md with complete Japanese documentation - Update language selector in README.md to include Japanese link - Update language selector in README.ko.md to include Japanese link 🤖 GENERATED WITH ASSISTANCE OF [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)	2025-12-15 23:38:03 +09:00
YeonGyu-Kim	bf39c83171	Fix: detect empty content messages in session-recovery error patterns Add pattern matching for 'content...is empty' format to detectErrorType function in session-recovery hook. This fixes detection of Anthropic API errors like 'The content field in the Message object at messages.65 is empty'. Previously only caught 'non-empty content' and 'must have non-empty content' patterns, missing this actual API error format. 🤖 Generated with assistance of [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)	2025-12-15 23:36:47 +09:00
YeonGyu-Kim	9b2048b3e8	feat(interactive-bash): block tmux output capture commands Block capture-pane, save-buffer, show-buffer, pipe-pane and their aliases in interactive_bash tool. Guide users to use bash tool instead for terminal output capture operations. - Add BLOCKED_TMUX_SUBCOMMANDS list in constants.ts - Add input validation in tools.ts to reject blocked commands - Update tool description with blocked commands documentation 🤖 GENERATED WITH ASSISTANCE OF [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)	2025-12-15 23:01:02 +09:00
YeonGyu-Kim	cea64e40b8	feat(#61 ): Implement fallback mechanism for auto-compact token limit recovery - Add FallbackState interface to track message removal attempts - Implement getLastMessagePair() to identify last user+assistant message pair - Add executeRevertFallback() to remove message pairs when compaction fails - Configure max 3 revert attempts with min 2 messages requirement - Trigger fallback after 5 compaction retries exceed - Reset retry counter on successful message removal for fresh compaction attempt - Clean fallback state on session deletion Resolves: When massive context (context bomb) is loaded, compaction fails and session becomes completely broken. Now falls back to emergency message removal after all retry attempts fail, allowing session recovery. 🤖 GENERATED WITH ASSISTANCE OF [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)	2025-12-15 21:19:44 +09:00
YeonGyu-Kim	151ebbf407	Suppress stderr output from Linux notification commands to fix WSL errors - Add 2>/dev/null to notify-send, paplay, and aplay commands - Prevents DBus error logs in WSL environments (Issue #47) - Maintains existing error handling behavior with .catch() 🤖 GENERATED WITH ASSISTANCE OF [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)	2025-12-15 21:13:18 +09:00
github-actions[bot]	e5ed5b528a	release: v2.1.0	2025-12-15 10:15:15 +00:00
YeonGyu-Kim	689c568e52	enhance(agents): Add comprehensive guardrails, Oracle examples, and specialized playbooks to OmO prompt - Add dedicated <Oracle> section with 4 use cases, situation-action table, and 5 concrete examples - Add <Failure_Handling> section: Type Error Guardrails, Build/Test/Runtime protocols, Infinite Loop Prevention - Add <Playbooks> section: 4 specialized workflows (Bugfix, Refactor, Debugging, Migration/Upgrade) - Enhance <Anti_Patterns> section with 5 new categories (Type Safety, Error Handling, Code Quality, Testing, Git) - Improve Oracle delegation guidance with practical patterns 🤖 Generated with assistance of OhMyOpenCode (https://github.com/code-yeongyu/oh-my-opencode)	2025-12-15 19:14:06 +09:00
YeonGyu-Kim	906d3040a9	Restore model to claude-opus-4-5 with thinking enabled, fix maxTokens to 64000 (correct max output for Opus 4.5 per Anthropic docs) 🤖 Generated with assistance of [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)	2025-12-15 19:14:06 +09:00
YeonGyu-Kim	424723f7ce	refactor(agents): Complete rewrite of OmO system prompt with Task Complexity assessment - Added comprehensive Task Complexity assessment before agent delegation (TRIVIAL/EXPLORATION/IMPLEMENTATION/ORCHESTRATION) - Redefined Explore agent as 'contextual grep' - cheap, parallel background agent for internal codebase search (Level 2 in search strategy) - Restricted Librarian agent to 3 explicit use cases: Official Documentation, GitHub Context, Famous OSS Implementation - Added mandatory delegation gate (GATE 2.5) for ALL frontend files (.tsx/.jsx/.vue/.svelte/.css/.scss) - NO direct edits allowed - Implemented obsessive Todo Management framework with BLOCKING evidence requirements for every action - Introduced comprehensive Search Strategy Framework with 3-level approach (Direct Tools → Explore → Librarian) - Restructured Blocking Gates with explicit Pre-Search gate and Pre-Completion verification - Enhanced Delegation Rules with clear agent purposes and parallelization strategies - Added Implementation Flow and Exploration Flow with phase-based workflows - Introduced Decision Matrix for quick action selection - Enhanced Anti-Patterns section with comprehensive BLOCKING rules for frontend work - Updated Tool Selection guide with clear preferences (Direct Tools > Agent Tools) - Improved parallel execution guidelines for explore/librarian agents - Strengthened verification protocol with evidence requirements 🤖 Generated with assistance of [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)	2025-12-15 19:14:06 +09:00
YeonGyu-Kim	3ba5e1abc9	Add date/time context to Librarian agent, emphasize NOT 2024 - librarian.ts: Add 'CRITICAL: DATE AWARENESS' section warning against 2024 searches - librarian.ts: Update examples to use 2025 instead of 2024 - utils.ts: Add librarian agent to envContext receiver list alongside OmO 🤖 GENERATED WITH ASSISTANCE OF [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)	2025-12-15 19:14:06 +09:00
YeonGyu-Kim	e324f0963b	refactor(agents): Restructure Librarian prompt with clear request classification flow - Reorganized prompt into Phase 0/1/2 workflow for systematic request handling - Introduced 4 request types (TYPE A/B/C/D) for proper classification - Removed ASCII art diagrams to simplify documentation - Reduced prompt from 330 to 232 lines while maintaining clarity - Improved flow between context gathering and decision-making phases 🤖 GENERATED WITH ASSISTANCE OF [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)	2025-12-15 19:14:06 +09:00
YeonGyu-Kim	9f636e1abc	fix(agents): enforce English prompting for all subagents (#58 ) - Add Language Rule (MANDATORY) section in OmO Delegation_Rules - Clarify that subagent prompts must always be in English - Update background-task tool documentation with English requirement - Update call-omo-agent tool documentation with English language rule - LLMs perform significantly better with English prompts - Improves consistency and performance across all agent-to-subagent communication 🤖 GENERATED WITH ASSISTANCE OF [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)	2025-12-15 19:14:06 +09:00
YeonGyu-Kim	5ce025fe92	feat(agents): prevent all subagents from accessing background_task tool Restrict background_task tool access for all spawned subagents (oracle, explore, librarian, frontend-ui-ux-engineer, document-writer, multimodal-looker) to prevent potential infinite recursion and unintended background task creation. 🤖 GENERATED WITH ASSISTANCE OF [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)	2025-12-15 19:14:06 +09:00
YeonGyu-Kim	153fa844d4	Add tmux availability check for conditional interactive_bash tool registration - Implement getTmuxPath() utility to detect tmux availability at plugin load time - Add getCachedTmuxPath() for retrieving cached tmux path - Add startBackgroundCheck() for asynchronous tmux detection - Conditionally register interactive_bash tool only when tmux is available - Silently skip registration without error messages if tmux not found - Export utilities from tools/interactive-bash/index.ts Tool now gracefully handles systems without tmux installed. 🤖 GENERATED WITH ASSISTANCE OF [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)	2025-12-15 19:14:06 +09:00
YeonGyu-Kim	2d2834f8a7	feat(agents): prevent oracle from calling task tool to avoid recursive invocation Add task: false to oracle agent's tools configuration to prevent the oracle agent from calling the task() tool, which could lead to recursive self-invocation. 🤖 GENERATED WITH ASSISTANCE OF [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)	2025-12-15 19:14:06 +09:00
YeonGyu-Kim	ab37193257	Clarify that today's date is NOT 2024 in envContext Prevents LLMs from mistakenly thinking it's 2024 when processing the date information. 🤖 GENERATED WITH ASSISTANCE OF [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)	2025-12-15 19:14:06 +09:00
YeonGyu-Kim	aa2f9a6ca5	OmO to not to call Explore every single time, only when required	2025-12-15 19:14:06 +09:00
YeonGyu-Kim	e326e2dd72	Interactive Bash Simpler	2025-12-15 19:14:06 +09:00
YeonGyu-Kim	f19a7a564e	Specify agents	2025-12-15 19:14:06 +09:00
YeonGyu-Kim	03a450131d	refactor(hooks): improve interactive bash session tracking and command parsing - Replace regex-based session extraction with quote-aware tokenizer - Add proper tmux global options handling (-L, -S, -f, -c, -T) - Add normalizeSessionName to strip :window and .pane suffixes - Add findSubcommand for proper subcommand detection - Add early error output return to avoid false state tracking - Fix tool-output-truncator to exclude grep/Grep from generic truncation - Fix todo-continuation-enforcer to clear reminded state on assistant response - Add proper parallel stdout/stderr reading in interactive_bash tool - Improve error handling with proper exit code checking 🤖 GENERATED WITH ASSISTANCE OF [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)	2025-12-15 19:14:06 +09:00
YeonGyu-Kim	c2e96f1ffe	feat(hooks): restrict background_task for task tool subagents - All subagents: disable background_task to prevent recursive spawning - explore/librarian: additionally disable call_omo_agent - Ensures task-invoked subagents use call_omo_agent instead of background_task 🤖 GENERATED WITH ASSISTANCE OF [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)	2025-12-15 19:14:06 +09:00
YeonGyu-Kim	e8e10b9683	fix(hooks): clear remindedSessions on assistant response to enable repeated continuation Fixed bug where remindedSessions was only cleared on user messages. Now also clears on assistant response, enabling the todo continuation reminder to be re-triggered on the next idle period after the assistant provides a response. 🤖 GENERATED WITH ASSISTANCE OF [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)	2025-12-15 19:14:06 +09:00
YeonGyu-Kim	5cbef252a3	feat(tools): add interactive_bash tool for tmux session management Add a new tool for managing tmux sessions with automatic tracking and cleanup: - interactive_bash tool: Accepts tmux commands via tmux_command parameter - Session tracking hook: Tracks omo-* prefixed tmux sessions per OpenCode session - System reminder: Appends active session list after create/delete operations - Auto cleanup: Kills all tracked tmux sessions on OpenCode session deletion - Output truncation: Registered in TRUNCATABLE_TOOLS for long capture-pane outputs 🤖 GENERATED WITH ASSISTANCE OF [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)	2025-12-15 19:14:06 +09:00
YeonGyu-Kim	2524c90850	fix(hooks): add lowercase tool names to truncator hooks Tool names in builtinTools are lowercase ('grep', 'glob') but truncator hooks were checking for capitalized names ('Grep', 'Glob'), causing truncation to never trigger and resulting in context window overflow. 🤖 GENERATED WITH ASSISTANCE OF [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)	2025-12-15 19:14:06 +09:00
YeonGyu-Kim	50112b97ea	feat(agents): inject environment context into OmO system prompt Add user time and system context to OmO agent prompt to help the model understand the temporal context of the conversation. Injected context includes: - Working directory - Platform (darwin/linux/win32) - Current date and time - Timezone - Locale Closes #51 🤖 GENERATED WITH ASSISTANCE OF [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)	2025-12-15 19:14:06 +09:00
YeonGyu-Kim	355fa35651	fix(hooks): respect previous message's agent mode in message sending hooks Message hooks like todo-continuation-enforcer and background-notification now preserve the agent mode from the previous message when sending follow-up prompts. This ensures that continuation messages and task completion notifications use the same agent that was active in the conversation. - Export findNearestMessageWithFields and MESSAGE_STORAGE from hook-message-injector - Add getMessageDir helper to locate session message directories - Pass agent field to session.prompt in todo-continuation-enforcer - Pass agent field to session.prompt in BackgroundManager.notifyParentSession Closes #59 🤖 GENERATED WITH ASSISTANCE OF [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)	2025-12-15 19:02:31 +09:00
YeonGyu-Kim	9aab980dc7	fix(session-recovery): fallback to filesystem when API parts empty When OpenCode API doesn't return parts in message response, read directly from filesystem using readParts(messageID). This fixes session recovery failures where tool_use IDs couldn't be extracted because API response had empty parts array. 🤖 GENERATED WITH ASSISTANCE OF [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)	2025-12-15 19:02:31 +09:00
github-actions[bot]	2920d5fe65	release: v2.0.4	2025-12-15 00:06:49 +00:00
YeonGyu-Kim	7fd52e27ce	refactor(non-interactive-env): use args.env instead of command prepending 🤖 GENERATED WITH ASSISTANCE OF [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)	2025-12-15 08:54:33 +09:00
YeonGyu-Kim	08481c046f	refactor(non-interactive-env): remove regex-based TUI blocking Keep only environment variable configuration and stdin redirection. 🤖 GENERATED WITH ASSISTANCE OF [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)	2025-12-15 08:49:19 +09:00
YeonGyu-Kim	192e8adf18	refactor(hooks): rename interactive-bash-blocker to non-interactive-env - Replace regex-based command blocking with environment configuration - Add cross-platform null device support (NUL for Windows, /dev/null for Unix) - Wrap all bash commands with non-interactive environment variables - Only block TUI programs that require full PTY - Update schema, README docs, and all imports/exports 🤖 GENERATED WITH ASSISTANCE OF [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)	2025-12-15 08:49:19 +09:00
Junho Yeo	5dd4d97c94	fix(auto-update-checker): resolve `unknown` version display and improve JSONC parsing (#54 )	2025-12-15 08:39:21 +09:00
YeonGyu-Kim	b1abb7999b	refactor(interactive-bash-blocker): replace regex blocking with environment configuration Instead of blocking commands via regex pattern matching (which caused false positives like 'startup', 'support'), now wraps all bash commands with: - CI=true - DEBIAN_FRONTEND=noninteractive - GIT_TERMINAL_PROMPT=0 - stdin redirected to /dev/null TUI programs (text editors, system monitors, etc.) are still blocked as they require full PTY. Other interactive commands now fail naturally when stdin is unavailable. Closes #55 via alternative approach.	2025-12-15 08:26:16 +09:00
YeonGyu-Kim	8618d57d95	add missing schema components	2025-12-14 22:34:55 +09:00
YeonGyu-Kim	4b6b725f13	feat(hooks): Add interactive-bash-blocker hook - Prevent interactive bash commands from being executed automatically - Block commands in tool.execute.before hook - Register in schema and main plugin initialization	2025-12-14 22:27:19 +09:00
YeonGyu-Kim	1aaa6e6ba2	fix(session-recovery): Add placeholder message for thinking-only messages - Add findMessagesWithThinkingOnly() to detect orphan thinking messages - Inject [user interrupted] placeholder for thinking-only messages - Expand index offset handling from 2 to 3 attempts for better error recovery - Use constant PLACEHOLDER_TEXT for consistency across recovery functions	2025-12-14 22:26:58 +09:00