Skip to content

CLITrigger

v0.2.27 Feature

This release adds 4 notable features for engineering teams evaluating rollout.

✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

ai-agents ai-automation claude claude-code codex codex-cli
+6 more
developer-tools electron gemini git-worktree multi-agent task-orchestration

Summary

AI summary

Broad release touches Highlights, Full commit list, readme, and Related docs.

Full changelog

v0.2.27 — Right-click context menus, pop-out focus fix, clearer docs graph

Release date: 2026-07-04
Previous version: v0.2.26

TL;DR

Terminal and task lists now have right-click context menus, clicking a pop-out terminal's dock chip actually brings its window to the front (previously it silently did nothing), and the Docs graph no longer claims "no markdown files" when your documents are merely hidden by .vaultignore — with a new ? button explaining how .vaultignore works.

Highlights

Right-click context menus in Terminal & Tasks lists

  • Right-click a terminal card for state-aware actions (open, start, continue, edit, stop, clean up, delete), or empty space to create a new terminal.
  • Right-click a task card for the same actions as its buttons/more-menu, or empty space to add a task.
  • Existing button UI is unchanged — the menu is an addition. The browser's native menu is preserved over inputs, textareas, and the terminal itself.

Fixed: pop-out terminal dock chip did nothing

Clicking the dock chip of a terminal opened in a separate window is supposed to bring that window forward, but Chromium ignores window.focus() calls outside a user gesture on the window itself. The chip now raises the window through two real paths — the opener's retained window proxy (inside the click gesture) and an Electron main-process IPC (restore/show/focus/moveTop, works even after the main window reloads). The "recall to center" action is back as a dedicated chip button.

Docs graph: honest empty states + .vaultignore help

  • When zero documents are scanned but .vaultignore has active patterns (e.g. the onboarding "hide everything" start), the graph now says all documents are hidden and how to unhide them — instead of the misleading "No markdown files found".
  • Graph load failures now show an error with a Retry button instead of being silently rendered as an empty vault.
  • A new ? button in the Docs sidebar opens a .vaultignore usage guide (gitignore syntax examples, the hide-everything onboarding state, default exclusions), with a shortcut to the editor.

Install / Update

npm i -g [email protected]

Desktop app — pick the right asset:

  • Windows (recommended): CLITrigger-Setup-0.2.27.exe — installer with Start Menu shortcut, uninstaller, and auto-update.
  • Windows (portable): CLITrigger-0.2.27.exe — run directly, no install; no shortcuts and no auto-update (grab new versions manually).
  • macOS: .dmg / Linux: .AppImage

Full commit list

  • e481a9e feat: 목록 우클릭 컨텍스트 메뉴 추가 + 팝아웃 창 포커스·회수 수정
  • 98abfa0 docs(release): 릴리스 노트에 Windows Setup/포터블 exe 구분 안내 추가 (템플릿 + v0.2.26)
  • 91cbe13 fix(vault): 그래프 빈 상태 오해 해소 — 전부 숨김/로드 실패 구분 + .vaultignore 도움말 버튼
  • aa17d41 docs(readme): 볼트/위키 기능 명칭을 문서(Docs)로 통일
  • 90da72e docs(readme): Buy Me a Coffee 후원 섹션 추가 (osgood)

Related docs

Full Changelog: https://github.com/HyperAITeam/CLITrigger/compare/v0.2.26...v0.2.27

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track CLITrigger

Get notified when new releases ship.

Sign up free

About CLITrigger

Self-hosted web UI for orchestrating Claude Code, Codex, and Gemini CLIs in parallel git worktrees. Features multi-agent discussion mode (architect/developer/reviewer debate before implementation), cross-project Morning Review Queue, scheduled execution with rate-limit auto-recovery, and a built-in Git client. MIT.

All releases →

Related context

Earlier breaking changes

  • v0.2.17 Deprecates Node 20 support; recommends using Node 22 LTS or newer.

Beta — feedback welcome: [email protected]