Gemini CLI — бесплатный аналог Claude Code с 2 млн токенов: полная настройка
The video demonstrates setting up Gemini CLI as a free alternative to Claude Code, featuring a 2 million token context window. The presenter walks through logging into an account, configuring autostart, and managing permissions within the CLI tool. The setup process reveals some quirks, including session-specific permissions and an initially empty process list.
Summary
The transcript covers a hands-on demonstration of Gemini CLI, presented as a free alternative to Claude Code with a 2 million token context window. The presenter begins by confirming they are logged into their account and that it is functioning correctly.
The main focus of the visible portion of the transcript is configuring autostart for the Gemini CLI tool. The presenter feeds configuration information directly into the CLI and instructs it to set up autostart automatically. During this process, the tool begins requesting permissions from the user.
A notable point raised by the presenter is the difference in how permissions are handled compared to Claude Code. In Gemini CLI, permissions granted during a session are scoped specifically to that session by default, whereas Claude Code grants permissions globally by default. The presenter notes they plan to configure full permissions later in the video.
Despite the tool reporting a successful setup, the presenter observes that the list of processes appears empty, indicating a potential issue or incomplete configuration that presumably gets addressed later in the video. The transcript provided is only a short excerpt (approximately 32 seconds of content shown), suggesting the full video contains a much more comprehensive walkthrough of the setup process.
Key Insights
- The presenter notes that Gemini CLI grants permissions on a per-session basis by default, in contrast to Claude Code which grants permissions globally by default.
- The presenter claims Gemini CLI is a free alternative to Claude Code, implying a significant cost advantage for users seeking AI coding assistance.
- The presenter demonstrates feeding raw configuration information directly into the CLI prompt and asking it to handle setup autonomously, showing an agentic workflow capability.
- Despite the tool self-reporting a successful autostart configuration, the presenter observes that the resulting process list is empty, suggesting the tool's self-verification may not always be reliable.
- The presenter indicates that full permissions configuration will be addressed later in the session, implying Gemini CLI supports broader permission scopes beyond the default session-limited behavior.
Topics
Full transcript available for MurmurCast members
Sign Up to Access