Platform Issues
Platform-specific problems
Platform Issues
Prompt-first procedure: Describe the outcome you want in your agent conversation. The agent should select and load the appropriate AIWG assets, explain material changes, request any needed approval, and report verification evidence. Exact commands and flags appear only in the CLI reference.
Problems specific to AI platforms (Claude Code, Factory AI, Warp Terminal).
Claude Code
CLAUDE.md Not Recognized
Symptoms: Claude doesn't understand AIWG commands or context.
Cause: CLAUDE.md missing AIWG section or not properly formatted.
Solution:
Use AIWG to complete this documented outcome: Solution
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.
Natural Language Not Working
Symptoms: Claude doesn't understand "transition to Elaboration" etc.
Cause: CLAUDE.md missing orchestrator context.
Solution:
Use AIWG to complete this documented outcome: Solution
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.
Multi-Agent Not Launching
Symptoms: Task tool not creating subagents, single-agent responses only.
Cause: Agents not deployed or permissions missing.
Solution:
Use AIWG to complete this documented outcome: Solution
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.
Factory AI
Custom Droids Not Enabled
Symptoms: `/droids` shows no custom droids, import option missing.
Cause: Custom Droids experimental feature not enabled.
Solution:
# Deployment should auto-enable, but if not:
droid
/settings
# Toggle "Custom Droids" under Experimental
Droids Not Appearing After Deploy
Symptoms: Files in `.factory/droids/` but not in Factory UI.
Cause: Factory requires manual import (security feature).
Solution:
droid .
/droids
# Press 'I' → 'A' → Enter
AGENTS.md Not Loading
Symptoms: Factory doesn't see project agents.
Cause: AGENTS.md not created or not updated.
Solution:
Use AIWG to complete this documented outcome: Solution
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.
Warp Terminal
WARP.md Not Loading
Symptoms: Warp AI doesn't recognize AIWG context.
Cause: WARP.md missing or Warp not reindexed.
Solution:
Use AIWG to complete this documented outcome: Solution
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.
File Too Large
Symptoms: Warp truncating or not loading full WARP.md.
Cause: WARP.md exceeds size limits with all agents embedded.
Solution:
Use AIWG to complete this documented outcome: Solution
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.
Context Not Updating
Symptoms: Old AIWG context showing after updates.
Cause: Warp caching old WARP.md.
Solution:
# Force reindex
/init
# Or restart Warp Terminal
Cross-Platform
Different Behavior Across Platforms
Symptoms: Same command works in Claude Code but not Factory/Warp.
Cause: Platforms have different orchestration capabilities.
Solution:
Use the right platform for your task:
| Task | Best Platform |
|---|---|
| Multi-agent orchestration | Claude Code |
| Simple commands | Any |
| Full artifact generation | Claude Code |
| Terminal workflows | Warp |
Sync Issues Between Platforms
Symptoms: Agents/config out of sync between platforms.
Cause: Manual updates to one platform's files.
Solution:
Use AIWG to complete this documented outcome: Solution
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.
Related
- Setup Issues - Installation problems
- Deployment Issues - Agent deployment problems