Troubleshooting
Common issues when installing or using Famasi Agents.
Run doctor first
Before debugging manually, run the diagnostic tool:
npx @famasi/agents@latest doctorThis checks:
- Which targets are installed
- Whether provider is linked
- MCP config presence
- Skill file existence
- Waitlist entries
Installation issues
”Command not found” or npx fails
Problem: npx @famasi/agents@latest install doesn’t work.
Fixes:
- Ensure Node.js 18+ is installed:
node --version - Clear npx cache:
npx clear-npx-cachethen retry - Try with explicit registry:
npx --registry https://registry.npmjs.org @famasi/agents@latest install claude-code
”Unknown install target”
Problem: npx @famasi/agents@latest install <target> says the target is unknown.
Valid targets:
claude-code codex generic-mcp openclawchatgpt and claude-ai are hosted surfaces — they don’t have install commands. Use the in-app connector instead.
Install runs but nothing seems to happen
Problem: The install command completes with a JSON output mentioning "mode": "waitlist".
Explanation: The CLI defaults to waitlist mode. Real installers are gated behind the v1 stage.
Fix:
# Enable real installsFAMASI_AGENTS_STAGE=v1 npx @famasi/agents@latest install claude-code
# Or use the flagnpx @famasi/agents@latest install claude-code --stage v1Authentication issues
”Authentication failed”
Fixes:
- Re-run the link command:
npx @famasi/agents@latest link provider --provider-id YOUR_PROVIDER_ID - Check your API key is correct and not expired
- Try rotating: ask the agent to “rotate my API key” (uses
refreshProviderApiToken)
“No provider linked”
Problem: Agent says it can’t find provider credentials.
Fix:
npx @famasi/agents@latest link provider --provider-id YOUR_PROVIDER_IDOr set the environment variable:
export FAMASI_PROVIDER_API_KEY=pk_live_...Full provider authentication details →
OTP not arriving
Fixes:
- Verify the phone number includes country code (e.g.,
+234...) - Check SMS isn’t blocked by your carrier
- Wait 60 seconds before requesting a new OTP
- Try a different phone number if available
Full individual authentication details →
MCP connection issues
”MCP server not responding”
Fixes:
- Verify
.mcp.jsonexists in your project root - Check it points to
https://mcp.famasi.ai/mcp - Test connectivity:
curl -I https://mcp.famasi.ai/mcp - Check your network/firewall allows HTTPS to that domain
”No tools available”
Problem: The MCP connection works but no tools appear.
Fixes:
- Provider tools require authentication — ensure
x-api-keyis set - Check
.mcp.jsonhas theheadersblock with your API key - Run
npx @famasi/agents@latest doctorto verify config
”Placeholder values present”
Problem: doctor command shows unset config values.
Fix: Run the link command to fill in real credentials:
npx @famasi/agents@latest link provider --provider-id YOUR_PROVIDER_IDPlatform-specific issues
Claude Code: Agent not using Famasi tools
Fixes:
- Check
.claude/agents/famasi-provider.mdexists - Verify
.mcp.jsonis in the project root - Restart Claude Code after installation
Codex: Skill not found
Fixes:
- Check
.famasi/skills/codex/famasi-provider/SKILL.mdexists - Verify
AGENTS.mdhas the## Famasi Providersection - Run
npx @famasi/agents@latest doctor
OpenClaw: Skill not loading
Fixes:
- Check
.famasi/skills/openclaw/famasi-patient/SKILL.mdexists - Verify the MCP URL environment variable is set:
Terminal window export FAMASI_MCP_URL=https://mcp.famasi.ai/mcp
Ordering issues
”No pharmacies found”
Fixes:
- Medication may not be in stock nearby — try a broader search term
- Check that location/coordinates are being sent correctly
- Try searching for the generic name instead of brand name
Widget not loading
Problem: Pharmacy selection or order tracking widget doesn’t appear.
Fixes:
- Widgets only work in ChatGPT and Claude.ai (hosted surfaces)
- Terminal clients (Claude Code, Codex) use text-based alternatives
- Check your browser allows iframes from the Famasi domain
Still stuck?
- Run
npx @famasi/agents@latest doctorand share the output - Check the CLI reference for all available commands and flags