DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to add Context Mode to Gemini CLI with one settings file with Context Mode

Install the npm package and register the MCP server and four hooks in settings.json.

Who it is forA developer who uses Gemini CLI on large repos and wants the same context savings without the Claude Code plugin.

The problemGemini CLI tool output can fill the context window quickly, and the default setup has no sandbox for it.

The outcomeThe MCP server shows as connected and the BeforeTool, AfterTool, PreCompress, and SessionStart hooks route large output through Context Mode.

What you need first

  • Claude Code v1.0.33+ for the plugin install, or Node.js >= 22.5 (or Bun) for the Gemini CLI setup
  • An existing AI coding agent session in a project you want to work on

Steps

  1. Run npm install -g context-mode.
  2. Add the mcpServers and hooks block from the README to ~/.gemini/settings.json.
  3. Restart Gemini CLI.
  4. Run /mcp list and confirm context-mode: ... - Connected.
  5. Optionally copy configs/gemini-cli/GEMINI.md into your project as ./GEMINI.md for routing instructions. (inferred, check the README)

Prompt for your agent

Install context-mode globally with npm, add the Gemini CLI settings from the context-mode README to ~/.gemini/settings.json, then run /mcp list in Gemini CLI. Report whether context-mode shows as Connected and list the four hooks that are registered.

Caveat. The README says Gemini CLI needs Node.js >= 22.5 or Bun, so check your runtime before editing the settings file.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page