Dashboard: Agents
The Agents tab provides configuration editors for Claude Code, Codex, and Gemini CLI tools.
Access: Klip: Open Dashboard (klip.openDashboard) > Agents tab
Overview
Each AI CLI has its own configuration file. Klip provides a visual editor to modify these settings without manually editing JSON/TOML files.
Agent Configuration
Claude Code
Claude Code uses a layered configuration system with multiple scopes:
| Scope | Location | Purpose |
|---|---|---|
| User | ~/.claude/settings.json | Global user preferences |
| User Local | ~/.claude/settings.local.json | Machine-specific overrides |
| Project | .claude/settings.json | Shared project settings |
| Project Local | .claude/settings.local.json | Personal project overrides |
Scope Precedence: Project Local > Project > User Local > User
Common settings:
- Model selection
- Permission behaviors (auto-approve, deny lists)
- MCP server configuration
- Custom slash commands
Claude Custom Commands
Claude supports custom slash commands stored in:
~/.claude/commands/(user-level).claude/commands/(project-level)
Klip shows discovered commands and lets you:
- View command definitions
- Open command files for editing
- Create new commands
Codex
Codex configuration lives in:
~/.codex/config.json
Common settings:
- Model selection
- Approval mode
- Provider configuration
Gemini
Gemini configuration is stored in:
~/.gemini/settings.json
Common settings:
- Model selection
- Safety settings
Visual Editor
The editor provides:
- Form view - Edit settings with dropdowns, toggles, and inputs
- Raw JSON/TOML view - Edit the configuration file directly
- Validation - Warns about invalid values
- Documentation - Hover for setting descriptions
MCP Server Configuration
Each agent can have MCP servers configured. The Agents tab shows which servers are enabled per agent.
For more comprehensive MCP management, see MCP Panel.
Related
- MCP Panel - Manage MCP servers across agents
- Dashboard: Settings - Klip settings
- Dashboard: Developer - API keys and logging