Gemini CLI marketing: launch your SaaS from the terminal

Most Gemini CLI marketing tips are about writing copy, research and content drafts. This page is about distribution: getting a SaaS listed on directories and launch platforms, one by one, with your own accounts. Every Gemini CLI fact below comes from its public docs or repository, with the date we checked it. Where a human has to step in, we say so.

What Gemini CLI can do for marketing, according to its docs

We read the docs and the repository on September 29, 2026. Gemini CLI ships new versions often, so check the linked source before you rely on a detail.

What it is: An open-source AI agent from Google that runs in your terminal, under the Apache 2.0 licence. Built-in tools cover file operations, shell commands, web fetching and Google Search grounding.github.com ↗ · Checked on September 29, 2026
Release pace: The latest stable release when we checked was v0.61.0, published on 23 September 2026. Preview and nightly builds come out in between.github.com ↗ · Checked on September 29, 2026
Free quota: Signing in with a personal Google account (Gemini Code Assist for individuals) allows up to 1,000 model requests per user per day. Per-minute limits and service availability also apply, and Gemini CLI picks which Gemini model serves each request.geminicli.com ↗ · Checked on September 29, 2026
Context files: Gemini CLI loads GEMINI.md files as persistent instructions: a global one in ~/.gemini, then files in the workspace and its parent folders. The context.fileName setting can add other names, and the docs use AGENTS.md as their example.geminicli.com ↗ · Checked on September 29, 2026
MCP servers: MCP servers go into the mcpServers object in settings.json, or are added with gemini mcp add. Unless a server is marked trusted, Gemini CLI asks before each of its tools runs.geminicli.com ↗ · Checked on September 29, 2026
Browser agent: A built-in browser agent, off by default, navigates pages, clicks and fills forms through the accessibility tree. It uses a bundled Chrome DevTools MCP server and needs Chrome 144 or newer.geminicli.com ↗ · Checked on September 29, 2026
Attaching to your Chrome: In the “existing” session mode the browser agent attaches to a Chrome that is already running, after you enable remote debugging at chrome://inspect/#remote-debugging. Form filling always needs your confirmation, whatever the approval mode.geminicli.com ↗ · Checked on September 29, 2026
Approval modes: The --approval-mode flag accepts default, auto_edit, yolo and plan. yolo auto-approves all actions; the older --yolo flag is deprecated.geminicli.com ↗ · Checked on September 29, 2026
Headless mode: With -p (or --prompt), or in a non-TTY environment, Gemini CLI runs non-interactively and can return plain text, JSON or a stream of JSON events.geminicli.com ↗ · Checked on September 29, 2026

Where Gemini CLI marketing automation needs a human

None of this is a flaw in Gemini CLI. Directories are built to stop unattended bots, and a terminal agent cannot click through a login challenge on your behalf. Plan for these stops before you start:

Sign-ins: Most directories need an account. Sign in yourself, in the Chrome that Gemini CLI is attached to. Google sign-in popups and new-device checks are yours to click, and your password never goes into the prompt.
CAPTCHA and bot checks: Cloudflare, reCAPTCHA and hCaptcha show up on many submit forms. You solve them in the same window. LaunchRepo’s playbooks never try to evade a challenge, and neither should a prompt you write.
2FA and email codes: Verification links land in your mailbox. If that mailbox is not open in the attached Chrome, you forward the code or click the link yourself.
Paid upsells: Many launch platforms push a paid fast track. Gemini CLI must be told plainly that it may not buy anything, and it has to tell a paid-only route apart from a free one.
Knowing what “live” means: A thank-you page is not a listing. Some platforms queue for weeks, some review by hand. Someone has to record what actually happened on each one and when to check again.

LaunchRepo with a browser agent →

GEMINI.md, extensions and launch context

Search for Gemini CLI marketing extensions or prompts and you will mostly find writing, SEO and social helpers. They do not tell Gemini CLI which directories still take free submissions, which fields each one rejects, or which listing went live.

Anything you add to settings.json, whether an MCP server or an extension, runs with your permissions. Read what it does before you install it, and keep trust off for servers you did not write, so every tool call still asks first.

LaunchRepo is not a Gemini CLI extension. It is a private GitHub repository: an AGENTS.md runbook, 299 directory playbooks in Markdown, a product template and a tracker. Gemini CLI reads it like any other folder, and context.fileName lets it load AGENTS.md the way it loads GEMINI.md.

Running LaunchRepo with Gemini CLI

LaunchRepo asks two things of an agent: read files, and drive a Chrome where you are signed in, through Chrome DevTools MCP. Going by its docs, Gemini CLI can do both. We have not published a test run with Gemini CLI, so treat this as a documented match, not a benchmark.

Clone the repository and load AGENTS.md: After purchase you accept a GitHub invitation and clone the private repository. Start Gemini CLI in that folder and add AGENTS.md to context.fileName, or simply tell it to read AGENTS.md first.
Let it run Python 3.10+: Workspace creation, record.py and the local dashboard use the Python standard library only. Gemini CLI runs them through its shell tool; if a sandbox you enabled blocks them, run them yourself.
Connect Chrome DevTools MCP to your Chrome: Follow BROWSER-SETUP.md: enable remote debugging in your everyday Chrome 144+, register Chrome DevTools MCP with --autoConnect under mcpServers, approve Chrome’s prompt, then check that the tab you can see actually moves.
Grant permissions once per product: What the agent may do (free sign-ups, final submissions, verification emails, badges) goes into authorizations.json during onboarding. Spending stays at zero.

Connect your coding agent to your Chrome →

Paste the public start prompt from START.md, unchanged. Note its first line: for best results it recommends Claude Code CLI or Codex CLI. That is our honest default. Gemini CLI can still follow the rest of the prompt, because the files and the browser route are the same.

START.md — paste as-is, in English

Recommend Claude Code CLI or Codex CLI in a terminal instead of the desktop apps for best results. If session metadata confirms desktop hosting, explicitly advise me to switch to the CLI and resume this same private workspace. Do not infer the host from a CLI engine version alone.

Read AGENTS.md, then follow "Start the dashboard for the owner". Create my private
workspace if I do not have one yet, start the dashboard, and give me the link.
Then lead ONBOARDING.md one phase at a time. Reuse recorded permissions instead of
asking again unless their scope is missing or conflicting. Actually test my visible
existing Chrome profile and intended identity as BROWSER-SETUP.md requires; use the
OS fallback if needed. Use one platform/browser worker by default. Build the normal
run only from suitable free-ready routes, keep research separate, and preserve any
draft that needs one exact human CAPTCHA/2FA action. Never claim browser control
bypasses or reduces those challenges.

The playbooks and instructions are English Markdown. Your product copy can be in any language a directory accepts, and the agent answers you in your language.

Start LaunchRepo in three steps →
LaunchRepo with Claude Code →

Who does what in a launch run

The same launch tasks, split between Gemini CLI on its own, Gemini CLI with LaunchRepo, and you.

Task	Gemini CLI alone	With LaunchRepo	You
Launch copy and descriptions	Yes, from your prompt	Fills forms from one product.json file	Approve the facts once
Which platforms to try	Google Search, unverified	Catalog of 299 dated playbooks	Choose the batch
Per-platform fields and rules	Works it out on each form	Playbook per platform	Fix a fact when asked
Sign-in, CAPTCHA, 2FA	Stops and asks	Stops, records a human handoff	Solve it in the same window
Record outcome and follow-up	Only if you build it	record.py, tracker, dashboard	Confirm “live” with a public URL

How it works →

Common mistakes

Running submissions in yolo or headless mode: Auto-approval and -p are fine for reading files or checking the tracker. Submissions need you nearby for sign-ins, challenges, form confirmations and the Chrome prompt.
Using the default browser profile by accident: The browser agent’s default “persistent” mode opens a separate Chrome profile where none of your accounts are signed in. Attach to your own Chrome instead.
Burning the daily quota on retries: The free tier counts model requests, and a long form with many retries uses them fast. Work in small batches and stop when a platform keeps failing.
Sending the whole catalog at once: Small batches, a duplicate search first and an identity check for each platform. That beats a burst of rejected or doubled listings.

Questions

Can Gemini CLI control a browser?

Yes. Its built-in browser agent uses Chrome DevTools MCP and needs Chrome 144 or newer; you can also add Chrome DevTools MCP yourself as an MCP server. In either case it can attach to a Chrome you already run, once remote debugging is on.

Is Gemini CLI free?

The tool is open source. With a personal Google account the documented free quota is up to 1,000 model requests per day, with per-minute limits on top. Paid Google plans and API keys come with their own limits.

Does Gemini CLI read AGENTS.md?

By default it looks for GEMINI.md. Set context.fileName in settings.json to include AGENTS.md, as the docs show, or ask it to read the file at the start of a session.

Can Gemini CLI do marketing for my SaaS?

Parts of it, yes. It can draft copy, research platforms and fill in forms in a browser. For a directory launch it lacks platform knowledge and a record of results, and it needs you for sign-ins, CAPTCHAs and 2FA.

Can Gemini CLI solve CAPTCHAs?

Nothing in its docs says so, and LaunchRepo does not try. A challenge becomes a recorded human handoff: you solve it in the same window, then the agent continues.

What does it cost?

Gemini CLI is free to install; the free quota or your Google plan covers model usage. LaunchRepo costs €99.98 once, at the launch price, for unlimited own products and any agent.

Give your agent the launch playbooks

The launch price is €99.98, paid once, for unlimited own products and any agent. It rises 20 % after every 20 sales.

See pricing