Gemini CLI
Install the Venom extension in Gemini CLI, authorize your organization, and check the connection.
Venom makes Gemini CLI multiplayer. Your teammates’ agents and yours share tasks, decisions, skills, and tools, whichever agent each person uses.
What you get in Gemini CLI.
The Venom extension configures the connection to Venom’s remote MCP server and loads a short context file, VENOM.md, in every session. The file tells Gemini to read the project and task before acting and to log what changed. Your organization’s own practices live in shared skills.
Install.
Install the extension folder from a clone of the plugin repository:
git clone https://github.com/venomlabs-dev/plugin venom-plugin
gemini extensions install ./venom-plugin/platforms/geminiDon’t install the repository root as a Gemini extension. To update, pull the repository and run:
gemini extensions update venomSign in.
Restart Gemini CLI and authorize Venom when prompted. Select your organization.
Check the connection.
Ask Gemini:
Use Venom to list the projects I work on. If there are none, tell me.An empty list is valid in a new organization. Follow the Quickstart to create a project and save a first result.
What guides Gemini CLI.
Venom Full’s hooks don’t cover Gemini CLI. Gemini gets the context file in every session and a one-line reminder at the top of every Venom tool response. A turn that never calls Venom gets no tool-response reminder. These ask; Gemini makes the tool calls.