---
title: "Share output from Gemini CLI — Krowk setup"
canonical_url: "https://krowk.com/docs/gemini-cli"
last_updated: "2026-10-01T21:55:10.708Z"
meta:
  description: "Install the krowk binary, add one line to GEMINI.md, and Gemini CLI publishes screenshots and recordings to permalinks that carry the commit and branch behind them."
  "og:description": "Install the krowk binary, add one line to GEMINI.md, and Gemini CLI publishes screenshots and recordings to permalinks that carry the commit and branch behind them."
  "og:title": "Share output from Gemini CLI — Krowk setup"
---

**Docs**

# **Krowk in Gemini CLI**

Install the binary, add one line to GEMINI.md, and the agent publishes the screen it changed rather than telling you about it.

[The CLI reference](https://krowk.com/docs/cli) [MCP setup](https://krowk.com/docs/mcp)

**Setup**

## **Two commands.**

1 — install

```
$ curl -fsSL https://krowk.com/install | bash
```

2 — check it landed

```
$ krowk doctor
```

Same two pieces as any other harness: put the binary on the path, then tell the agent when to use it. Gemini CLI reads standing instructions from `GEMINI.md`, so the instruction is the whole integration.

## The instruction

Put this in `GEMINI.md` at the repository root, or in `~/.gemini/GEMINI.md` for every project.

GEMINI.md

```
After any visual change, capture it (screenshot if static, a short screen recording if it is an interaction) and publish it with the krowk skill. If the skill is missing or fails, run `krowk help --json`, then `krowk push FILE --title "what changed" --json`, and paste `paste.url` where you report the work.
```

It names a fallback on purpose. There is no skill for the agent to find here, so it reads `krowk help --json` and works from that rather than inventing a flag.

## What it records

Gemini CLI does not yet publish a variable Krowk recognises, so the harness is not detected on its own. Export `KROWK_AGENT=gemini-cli` and the card names it. Export `KROWK_MODEL` and the card names the model as well; a `gemini` prefix is enough for the provider to be recorded. Git supplies the rest — repository, commit, branch, dirty flag.

## MCP, if you would rather

Gemini CLI speaks MCP. Add `krowk-mcp` as a stdio server and the agent gets `krowk_push` as a tool instead of a command — same client, same refusals.

\~/.gemini/settings.json

```
{
  "mcpServers": {
    "krowk": { "command": "krowk-mcp" }
  }
}
```

## **One line in GEMINI.md, and the evidence stops dying with the terminal.**

No account needed for the first push.

[The CLI reference](https://krowk.com/docs/cli) [See the pricing](https://krowk.com/pricing)