bifrost-debuglisted

# Bifrost Diagnostics Work through this decision tree to isolate and fix the problem. ## 1. Check credentials are set (shell env, or plugin config) On the CLI: ```bash echo "URL set: ${BIFROST_URL:+yes}${BIFROST_URL:-NO — missing}" echo "VK set: ${BIFROST_VK:+yes}${BIFROST_VK:-NO — missing}" ``` If missing: `export BIFROST_URL=https://<your-gateway-host>/mcp` and `export BIFROST_VK=vk_<your-key>` (add both to `~/.zshrc` or `~/.bashrc`). On Desktop and claude.ai there is no shell, so this check does not apply. Credentials come from the plugin's three install-time config values (`gateway_url`, `virtual_key`, `oauth_client_id`). Run `/plugin configure` to view or change them. Symptom if the key is wrong/missing: 401 or 403 from every bifrost tool call. ## 2. Check the bifrost MCP server is registered ```bash claude mcp get bifrost 2>/dev/null || echo 'bifrost: MISSING at user scope' ``` The server can come from either the plugin's shipped `.mcp.json` (plugin installed + enabled → shows up in `/mcp`) or a user-scope registration. If neither: run `/bifrost-mcp-setup` for manual wiring instructions. Then restart Claude Code for CC to pick up the change. ## 3. Check gateway reachability ```bash curl -s -o /dev/null -w "%{http_code}" \ -H "x-bf-vk: ${BIFROST_VK}" \ "${BIFROST_URL}" ``` Expected: 200 or 405 (OPTIONS probe). 401 → bad VK. Timeout / connection refused → gateway down or `BIFROST_URL` wrong (contact the gateway operator). ## 4. Check the gateway's memory