AI Environment
CLI Tools Overview & Comparison
Compare agentic AI CLI tools (Claude Code, Antigravity CLI, OpenCode) and GUI options (Cherry Studio) to choose the best fit for your research workflow.
Reference page for: agentic CLI tool choice. Other pages link here before sending readers into a specific setup guide.
Overview
The Research Memex workflow works with both GUI and CLI tools. GUI tools are better for early exploration and teaching; CLI tools are better when the work becomes file-based, repeatable, and auditable.
Info
Most researchers should start with one GUI and one CLI. Cherry Studio covers model comparison and knowledge bases. A CLI agent covers project files, scripts, and longer running research workflows.
The Current Landscape
Cherry Studio
- Visual multi-model workspace
- Good first interface for API keys, knowledge bases, and MCP servers
- Useful for teaching, comparison, and non-terminal researchers
- Full guide: Cherry Studio Setup
Claude Code
- Anthropic's terminal agent
- Strong fit for deep project work, code, and research-writing infrastructure
- Best when you want Claude as the main workspace model
- Full guide: Claude Code Setup
Antigravity CLI
- Google's current terminal-agent path for consumer and free Gemini CLI users
- Good fit for Google-account workflows, SSH use, and Antigravity 2.0 continuity
- Not a replacement for direct Gemini API setup in Cherry Studio, OpenCode, or Vox
- Full guide: Antigravity CLI Setup
OpenCode
- Multi-provider terminal UI
- Good fit for comparing GPT, Claude, Gemini, DeepSeek, Kimi, GLM, Qwen, xAI, and local models
- Best when model choice is the experiment
- Full guide: OpenCode Setup
Comparison Table
| Feature | Cherry Studio | Claude Code | Antigravity CLI | OpenCode |
|---|---|---|---|---|
| Interface | GUI | CLI | CLI | TUI |
| Provider model | Many providers | Claude | Google Antigravity/Gemini paths | Many providers |
| Best role | Exploration and teaching | Primary project workspace | Google terminal-agent workflow | Provider comparison |
| Direct API keys | Yes | Usually no | No for normal sign-in flow | Yes |
| MCP support | Full | Full | Use documented settings/plugin paths only | Depends on host/provider config |
| Project memory | Knowledge bases and chats | Project files + Claude config | Project files + Antigravity settings/plugins | Project config |
| Cost shape | Provider API usage | Subscription/API, depending on plan | Google account/enterprise path | Provider API usage |
| Best for | Starting out | Deep work | Google-agent continuity | Model experimentation |
Which One Should You Use?
If you are new to the workflow
Start with Cherry Studio. It makes providers, API keys, knowledge bases, and MCP servers visible. Add a CLI only after you have a real project folder and repeated tasks.
If you want the strongest single-agent workspace
Use Claude Code. It is the default high-trust workspace in this site because it handles repository context, file edits, command execution, and research infrastructure cleanly.
If you used Gemini CLI
Move the terminal-agent workflow to Antigravity CLI. Keep direct Gemini API work where it already belongs: Google AI Studio, Cherry Studio, OpenCode, Vox, or another provider client.
If you want to compare models
Use OpenCode. It keeps the tool constant while you vary the model/provider, which is the right shape for model-selection experiments.
Research Phases
| Research phase | Recommended surface | Reason |
|---|---|---|
| First setup | Cherry Studio | Lowest friction for provider keys and knowledge bases |
| Literature exploration | Cherry Studio or OpenCode | Easy model comparison and corpus experiments |
| File-based analysis | Claude Code or Antigravity CLI | Agents can work inside a project folder |
| Multi-model challenge | OpenCode or Vox MCP | Same prompt across different providers |
| Final writing and infrastructure | Claude Code | Strong project reasoning and repo operations |
Terminal Basics
If you are new to terminals, these commands are enough to begin:
cd ~/Documents/Research-Project
pwd
lsLaunch the CLI you installed:
claude
agy
opencodeExit most terminal tools with exit, /exit, or Ctrl+D, depending on the tool.
API Keys vs Sign-In
Do not collapse every tool into the same auth pattern.
| Auth pattern | Used by | Notes |
|---|---|---|
| Provider API key | Cherry Studio, OpenCode, Vox | Use OPENAI_API_KEY, ANTHROPIC_API_KEY, GOOGLE_API_KEY, GEMINI_API_KEY, etc. only when the client calls that provider directly. |
| Product sign-in | Claude Code, Antigravity CLI | The tool handles the session. Do not invent provider env vars unless the official docs say to. |
| Enterprise project binding | Antigravity CLI, some Claude/Google setups | Follow your organization's onboarding path. |
Setup Guides
Troubleshooting
Large-context Gemini model access
Use the Gemini API path in API Keys Setup, or use a client such as Cherry Studio, OpenCode, or Vox. Antigravity CLI is the terminal-agent product path, not the general Gemini API setup page.
Old Gemini CLI notes
If the note is about terminal-agent usage, migrate it to Antigravity CLI. If it is about model/API access, keep the Gemini API-key guidance.
Choosing a single CLI
Use Claude Code if you want one primary workspace. Use OpenCode if provider comparison matters more than a single polished agent. Use Antigravity CLI if you specifically want the Google Antigravity path.