Deployment Issues

Deployment problems

Deployment 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 with agent and command deployment.

Agents Not Found

Symptoms: "Agent not found", subagent calls fail, Task tool errors.

Cause: Agents not deployed to project.

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.

Commands Not Found

Symptoms: Slash commands not recognized, "/command not found".

Cause: Commands not deployed to project.

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.

Duplicate Commands in Command Palette

Symptoms: Slash commands appear twice in Claude Code (or another provider's command palette) after running the agent-owned use operation.

Cause: An old `.claude/commands/` directory exists alongside the new `.claude/skills/` directory. Both locations are scanned, so every overlapping file produces two entries.

Solution: Remove the legacy commands directory:

rm -rf .claude/commands/

Then re-run the agent-owned use operation to ensure skills are fully deployed:

Use AIWG to complete this documented outcome: Then re-run the agent-owned use operation to ensure skills are fully deployed
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

Prevention: the agent-owned use operation normally prompts to delete the commands directory automatically (the commands → skills migration step). If you skipped that prompt or passed the skip-commands-migration option, remove the directory manually as shown above.

Agent Access Denied

Symptoms: "Permission denied" when agent tries to read AIWG files.

Cause: Claude Code settings missing read permission for AIWG installation.

Solution:

1. Open `.claude/settings.local.json` (or create it) 2. Add read permission:

{
  "permissions": {
    "allow": [
      "Read(/home/YOUR_USER/.local/share/ai-writing-guide/**)"
    ]
  }
}

Replace `YOUR_USER` with your actual username.

Outdated Agents

Symptoms: Agents missing new features, old behavior.

Cause: Project has old agent versions.

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 Droids Not Loading

Symptoms: Droids not appearing in Factory `/droids` menu.

Cause: Factory requires manual import after deployment.

Solution:

# In Factory CLI
droid .
/droids
# Press 'I' to import
# Press 'A' to select all
# Press Enter to confirm

See Factory Quickstart for details.

Warp Not Loading WARP.md

Symptoms: Warp AI doesn't recognize AIWG commands/context.

Cause: WARP.md not in project root 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.