When analyzing large codebases or multiple files that might exceed context limits, use the Gemini CLI with its massive context window. Use gemini -p to leverage Google Gemini's large context capacity.
Use the @ syntax to include files and directories in your Gemini prompts. The paths should be relative to WHERE you run the gemini command:
| #!/usr/bin/env bash | |
| set -euo pipefail | |
| issue=$1 | |
| ~/.claude/local/claude \ | |
| "Start working on issue #$issue | |
| - Keep an open mind. Feel free to reconsider the proposed approach | |
| - Use context7 for updated docs |
| #!/usr/bin/env zsh | |
| # Multi-project worktree manager with Claude support | |
| # | |
| # ASSUMPTIONS & SETUP: | |
| # - Your git projects live in: ~/projects/ | |
| # - Worktrees will be created in: ~/projects/worktrees/<project>/<branch> | |
| # - New branches will be named: <your-username>/<feature-name> | |
| # | |
| # DIRECTORY STRUCTURE EXAMPLE: | |
| # ~/projects/ |
Excellent. This is a fantastic comparison task. Let's break down the technical differences between Gemini CLI and Codex CLI based on their file structures and documentation, and then determine which one might be "better" for different use cases.
| Feature | Gemini CLI | Codex CLI |
|---|---|---|
| Core Language | TypeScript (Node.js) | Hybrid: Rust & TypeScript |
| Architecture | Client/Server (both in TypeScript) | Hybrid: Rust core/TUI with a parallel JS/React TUI |
| Sandboxing | Docker/Podman or macOS Seatbelt | Rust-based execpolicy engine, macOS Seatbelt, Linux Landlock |
| UI Framework | React & Ink (TypeScript) | React & Ink (JS) AND Ratatui (Rust) |
I have a large codebase that I want to understand better through visual architecture diagrams. Please analyze the project structure and create comprehensive Mermaid diagrams that help me understand the codebase at different levels of detail.
First, explore the codebase to understand:
Analyze this codebase and create a multi-level interactive dependency graph visualization as a single HTML file.
Level 1 - System Overview (40,000ft view):
Level 2 - Module View (10,000ft view):
Date: June 19, 2025
Platform: MacOS
Project: TikAPI_MCP
Environment: /Users/tengjizhang/projects/flashbots_x/TikAPI_MCP
The TikAPI MCP server was experiencing failures when making requests to the TikAPI service, with empty error messages: "An error occurred while requesting TikAPI: ". This prevented the /resources/read and search functionality from working properly.
Whether you’re juggling multiple windows and panes across nested tmux sessions, having a single, ergonomic shortcut to switch and zoom panes can save you valuable time. This snippet extends your outer tmux configuration to bind <prefix> g for a seamless, two-step pane selection: un-zoom the current pane, display a long-lasting pane number overlay, and automatically zoom the pane you choose—all in one intuitive command.
Use this snippet in your ~/.ubertmux to bind <prefix> g so it:
This document outlines the structured development workflow that ensures quality, consistency, and efficiency when using Claude for software development projects.
Our workflow is built on three fundamental principles:
