Gemini CLI

Vendor: Google Install name: gemini-cli Status: GA Native config: project-local GEMINI.md and .gemini/

Installation

apothem install --harness gemini-cli --project /path/to/project

The adapter is project-scoped. It installs the project GEMINI.md, converts Apothem commands to Gemini TOML slash commands, normalizes local helper definitions, and places non-native support cohorts under .gemini/.apothem/support/.

Files written:

GEMINI.md
.gemini/commands/*.toml
.gemini/agents/*.md
.gemini/skills/
.gemini/.apothem/support/

Profile-to-native-config mapping

The adapter reads Apothem's shared cohorts and routes each one through a Gemini-compatible surface. Markdown rules, templates, and hook material remain under .gemini/.apothem/support/ because they are support material, not a Gemini-native rules directory.

Compatibility notes

~/.gemini/ remains user-scope territory for tools that use a global Gemini profile. The Gemini CLI adapter writes only to the project passed through --project.

Verification

apothem verify --harness gemini-cli --project /path/to/project

The verify command confirms that:

1. The native config exists at the expected path.
2. All mandatory fields from the shared profile are present.
3. The adapter-specific verification routine reports success.

Updating

apothem update --harness gemini-cli --project /path/to/project

Refreshes GEMINI.md, converted commands, local helper definitions, installed skills, and the .gemini/.apothem/support/ support tree.

Uninstalling

apothem uninstall --harness gemini-cli --project /path/to/project

Removes the native config files written by the adapter. The shared profile YAML and Apothem engine are unaffected.

Conformity gate

python -m apothem.conformity.gate --all .

Troubleshooting

Configuration knobs

See also

• All harnesses — the full catalog of supported tools
• Install guide — install Apothem into this harness
• apothem harnesses reference — list and inspect adapters from the CLI