Connectors

Connectors are how Ask The W keeps the operating view current. Manage them during onboarding or from /connectors.

For AI-native product teams, connectors feed the judgement layer. The useful source is the one that preserves why a product decision changed, who or what agent changed it, and which outcome it should move.

Each connector shows whether it is active, pending, suggested, or paused, plus the last sync details and available action buttons.

Product reference

Find it in Ask The W at /connectors. The top connected-sources section shows active sources, last sync state, refresh actions, status toggles, and management buttons for each connector.

Connector categories at a glance

• Native: GitHub, URL watchers, paste-link, paste-context, upload-file, and the Ask The W Plugin.
• Hosted via Composio: Linear, Slack, Notion, plus the wider hosted catalog. One authorization flow can support many destinations.

Connect one core connector first. Add secondary connectors after the first judgement map is useful.

GitHub (native OAuth)

GitHub is the most common first source when code, PRs, comments, reviews, and commits define decision outcomes.

Open Connectors, choose GitHub, connect the account, choose repository scope, and confirm the allowlist.

GitHub contributes pull requests, comments, review notes, repo activity, and commit-driven decisions. When a repo list is pending, open the GitHub selector and choose repositories intentionally.

Hosted via Composio: Linear, Slack, Notion, others

Linear, Slack, and Notion connect through the hosted Composio authorization flow. Click Connect, authenticate on the provider, and return to Ask The W with the connector live.

Use Linear for issue movement, Slack for coordination threads, and Notion for docs, notes, and plans.

If a connector is already active, Ask The W shows its current state instead of replaying authorization.

Hosted connector redirects are accepted only from trusted Composio HTTPS destinations. Duplicate webhook deliveries are ignored so retries from a provider should update connector state once, not create repeated source activity.

URL watchers

URL watchers keep checking a public page after you add it with Paste Link. A new signal appears only when the page changes, so quiet pages do not clutter the decision feed.

Use watchers for pages you own or are allowed to monitor, such as pricing, roadmap, changelog, docs, policy, or partner status pages.

You control the URL, optional display name, check interval, and whether the watcher is on or off. The first check sets the baseline. Later changes create new signals linked into the same outcomes and decision views as your other sources.

Watcher states:

• Watching on means checks are running.
• Needs attention means recent checks failed repeatedly.
• Paused means checks are off until you turn them back on.

Paste a link

Use Paste Link for public docs pages, repo pages, public roadmaps, and strategy pages. Paste the URL, decide whether linked pages should be crawled, then confirm ingestion.

Ask The W fetches the page, optionally includes linked pages, and maps resulting signals to outcomes and teams.

Paste context

Paste Context is best for project notes, whiteboard summaries, chat exports, focused PRDs, and customer-call excerpts.

Keep content focused. Include outcomes and owners if known. Use Upload File for material over 1 MB.

Rich HTML pasted from docs or wikis is cleaned into readable text before signal extraction. Large pastes can take longer to process, so keep the panel open until the progress state finishes.

Upload a file

Upload docs, transcripts, notes exports, or planning artifacts. Files work best when they mention owners, goals, deadlines, tradeoffs, or changes.

Uploads support text-heavy files up to 10 MB. Avoid broad archives when only one section matters.

Best files include PRDs, launch plans, strategy memos, meeting transcripts, research summaries, customer notes, sales call exports, and operating plans. If a readable file does not update decisions or outcome signal counts, try a narrower excerpt with clearer owners, changes, tradeoffs, and product judgement.

The Ask The W Plugin (coding agents)

Use the plugin when Codex or Claude Code makes decisions worth retaining. It captures compact checkpoints, local signals, local decisions, and optional workspace uploads.

See Install the Ask The W Plugin for commands, prompts, token behavior, privacy, and troubleshooting.

Setup checklist

1. Connect the highest-signal connector first.
2. Wait for the first signals to process.
3. Check that decisions map to outcomes and owners.
4. Review connector status and last sync.
5. Add another connector only after the first one improves the operating map.

During onboarding, use the first connector to prove whether Ask The W is learning useful signals for your team. After that, manage day-to-day connector health from /connectors.

When a connector misbehaves

Check status, workspace, authorization, scope, and latest sync time.

For plugin issues, issue a fresh workspace install command from /connectors, rerun the installer, and confirm capture_session_signal is allowed in the coding agent.

For hosted connectors, reconnect only when authorization has expired or the provider scope changed. For URL watchers, update the URL or pause the watcher if repeated failures are expected. For uploads and pastes, use narrower source material when broad context creates weak or unrelated signals.