version: "1.0.2" name: aw:configure description: Check and set up the aweb channel connection. Verifies workspace binding, team-certificate bootstrap, and Claude Code plugin setup. allowed-tools: Bash(aw ), Bash(claude ), Bash(test ), Bash(ls )

Configure aweb channel

Diagnose and fix the aweb channel setup for this project.

Steps

1. Check workspace binding.

``bash test -f .aw/workspace.yaml && echo "OK" || echo "MISSING" test -f .aw/team-cert.pem && echo "CERT OK" || echo "CERT MISSING" ``

If .aw/workspace.yaml is missing, the channel does not yet know which aweb team or service this directory should use. Do not guess. Tell the user to initialize or join the workspace through the correct source first, for example:

``bash aw init ``

Or, when they have an explicit invite/service/BYOT source:

``bash aw id team accept-invite <token> AWEB_URL=<server-url> aw init aw service init --service <service-url> --team <team:namespace> ``

After .aw/workspace.yaml exists, continue with the channel plugin checks below. Do not instruct the user to use legacy project bootstrap commands.

1. Verify the workspace is valid.

``bash aw workspace status ``

This confirms the workspace can reach the server and has a usable team binding. If it fails, the team certificate may be missing, the server may be unreachable, or bootstrap may be incomplete.

1. Ensure the Claude Code channel plugin.

``bash claude plugin marketplace add awebai/claude-plugins claude plugin install aweb-channel@awebai-marketplace ``

These commands are non-interactive and idempotent. aw init --setup-channel runs the same plugin setup. Do not configure a per-home .mcp.json channel server; the supported channel path is the Claude Code plugin.

1. Report status. Summarize what was found and what the user still needs to

do. If everything is configured, tell the user to start Claude Code with this exact line:

``bash claude --dangerously-skip-permissions --dangerously-load-development-channels plugin:aweb-channel@awebai-marketplace ``

Tell them why both flags are there: channel messages are delivered to the session only in bypass-permissions mode today — in Claude Code's default auto mode (and plan mode) the notification arrives and is silently not surfaced, so without --dangerously-skip-permissions there are no wake-ups. Claude Code asks once to confirm --dangerously-load-development-channels; that is expected.

1. Offer removal of an old polling fallback after delivery works. Plugin

installation alone does not prove delivery. Once the user confirms channel or host broker delivery, explain the optional local cleanup:

``bash aw init --remove-notify-hook ``

Run it when the user asks to remove the fallback. It backs up the historical project .claude/settings.json, removes only exact aw notify commands under PostToolUse, and preserves other settings bytes. Do not remove hooks merely because init, an upgrade or plugin installation ran. --setup-hooks remains an explicit Claude Code fallback for chat notices after tool calls, with no mail or idle wake-ups; it does not configure Codex hooks.

1. Mention Pi. Pi is the other maintained wake-up path: `pi install

npm:@awebai/pi@latest, then start pi` in the workspace. Mail and chat wake the session, with the sender's verification shown.

Reference model: docs/aweb-sot.md, docs/awid-sot.md, and docs/agent-guide.md.