Gemini CLI Warp
https://github.com/warpdotdev/gemini-cli-warp- Category
- Developer Tools
- Rank
- No. 1692Tools index
Previous survey · No. 1698 ·
- Pricing
- Open Source
- Type
- TOOL
- Builder
- warpdotdev
- GitHub
- 7 stars
- Date
About
Gemini CLI extension for notifications and other integrations with the Warp terminal.
What it does
It turns Gemini lifecycle events into Warp alerts and session-state updates. Shell hooks capture prompts, completed responses, permission requests, idle waits, and finished tool activity, then send structured JSON through terminal escape sequences.
Why it's ranked here
The design is narrow but disciplined. It covers the moments when an unattended agent needs attention, negotiates protocol compatibility, avoids duplicate completion alerts, and includes automated payload and routing tests.
What's good
Notifications carry useful context, including truncated prompts, responses, tool details, and project information. Compatibility checks suppress structured output when Warp cannot safely render it, while protocol negotiation caps payloads to the supported format.
Tradeoffs
It only works with Warp and requires Gemini CLI plus jq. Unsupported or unverifiable Warp builds receive no fallback notification. Completion summaries truncate prompts and responses, so detailed results still require returning to the terminal.
How to use it well
It suits developers who run longer Gemini tasks in Warp and regularly switch contexts. Install it through Gemini’s extension command, restart the CLI, and tune alert behavior in Warp. It does not provide agent execution, tool approval, or terminal support outside Warp.
Technical notes+
hooks/hooks.json registers SessionStart, AfterAgent, Notification, BeforeAgent, and AfterTool command hooks. scripts/build-payload.sh uses jq to construct versioned event payloads and negotiate the protocol through WARP_CLI_AGENT_PROTOCOL_VERSION. scripts/should-use-structured.sh gates emission using the advertised protocol, WARP_CLIENT_VERSION, and channel-specific compatibility thresholds. scripts/warp-notify.sh writes OSC 777 notifications to /dev/tty. tests/test-hooks.sh covers payload fields, escaping, version negotiation, compatibility gating, and silent routing, while .github/workflows/test.yml runs shell tests on pushes and pull requests.
Observed
- License
- MIT License
- Primary language
- Bash shell scripts
- Install surface
- Gemini CLI extension command using a GitHub URL or local path
- Interface
- Gemini CLI lifecycle hooks emitting structured OSC 777 terminal notifications
- Platform support
- Warp on macOS, Linux, or Windows
- Runtime requirements
- Warp terminal, Gemini CLI v0.26.0 or newer, and jq
- Testing
- Shell test suite with automated CI execution
Read from README.md, LICENSE, gemini-extension.json, hooks/hooks.json, scripts/on-stop.sh, tests/test-hooks.sh, scripts/warp-notify.sh, scripts/build-payload.sh, scripts/on-notification.sh, scripts/on-post-tool-use.sh, scripts/on-prompt-submit.sh, scripts/on-session-start.sh, scripts/should-use-structured.sh, .github/workflows/test.yml.
What it can do
Send notifications to Warp terminal
Notification message or event data → Visual notification in Warp terminal interface
Execute Gemini AI commands from terminal
CLI commands with prompts or queries → AI-generated responses or content
Integrate Gemini API with Warp terminal workflows
Terminal commands and Gemini API calls → Processed results within terminal environment
Display Gemini responses in terminal format
Gemini AI output data → Formatted text display in Warp terminal
Configure CLI extension settings
Configuration parameters and preferences → Updated extension settings and behavior
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.