AI Tools Troubleshooting
Codex CLI
Section titled “Codex CLI”/goal Not Visible
Section titled “/goal Not Visible”codex features list | rg '^goals'The expected state is stable true. If it is false, reinstall the repo-managed config and restart Codex:
make stow-codexcodex features enable goalsThe dotfiles config also pins features.goals = true directly in ~/.codex/config.toml.
Config Health
Section titled “Config Health”codex doctor --summary --asciicodex mcp listcodex plugin listOnly ~/.codex/config.toml is managed by this repo. Auth files, history, SQLite state, logs, and caches should remain local.
miudb MCP
Section titled “miudb MCP”Check the shared miudb MCP entry from each host:
codex mcp list | rg miudbclaude mcp get miudbmiudb describe mcp serve --output jsonCursor reads the same server from ~/.cursor/mcp.json.
{ "command": "miudb", "args": ["mcp", "serve", "--transport", "stdio"]}CodeCompanion Issues
Section titled “CodeCompanion Issues”API Key Problems
Section titled “API Key Problems”# Check Gemini API keyecho $GEMINI_API_KEY
# Set API key temporarily:lua vim.env.GEMINI_API_KEY = "your-key-here"Chat Not Responding
Section titled “Chat Not Responding”# Check networkping generativelanguage.googleapis.com
# Restart CodeCompanion:CodeCompanion resetSupermaven Issues
Section titled “Supermaven Issues”Suggestions Not Appearing
Section titled “Suggestions Not Appearing”# Check if Supermaven is running (auto-starts)# Try restarting Neovim
# Ensure not in a large file (>100KB can disable AI)Performance Issues
Section titled “Performance Issues”# Supermaven uses proprietary model# Check system resources# Large files may slow suggestionsDatabase (miudb) Issues
Section titled “Database (miudb) Issues”Connection Failures
Section titled “Connection Failures”# List saved connections:MiuDBConnections
# Select active connection:MiuDBSelectConnection
# Check miudb CLI directlymiudb connections list --output jsonQuery Problems
Section titled “Query Problems”# Run from Neovim:MiuDBQuery
# Run from shell for debuggingmiudb query run --connection <name> --sql 'select 1 as one' --output json