Type: Enhancement (feature request from user feedback — not a bug)
Motivation: From the thread: "I've detected you have Claude Code / Claude Desktop installed, which probably indicates you have an Anthropic account — would you like to connect this app to that account to use the AI assistant features? Greatly enhances how this tool works." A proactive, detection-driven prompt turns "AI is off until you go configure it" into a one-click opt-in.
Proposal: On first run (or when no AI provider is configured), detect signs that the user already has a relevant account/tooling installed and offer to connect:
- Claude Code (CLI) / Claude Desktop → offer to connect an Anthropic account.
- ChatGPT desktop app → offer to connect OpenAI.
- An existing local Ollama install → offer to use it directly (no account needed).
Detection should be cheap and privacy-respecting: look for the apps' presence (install registry entries / well-known paths / CLI on PATH) — do not read their credentials or config secrets. The prompt is just an onboarding nudge that routes the user into the appropriate connect flow.
Depends on / relates to:
- The OAuth sign-in flow (separate issue) — the "connect Anthropic/OpenAI" buttons need a real auth path, which has open feasibility questions; this issue is the detection + onboarding prompt, not the auth mechanism.
- One-click local-model setup (#— the Ollama onboarding issue) for the "use your local Ollama" branch.
Keep it dismissible and non-nagging (offer once; respect "no").
Type: Enhancement (feature request from user feedback — not a bug)
Motivation: From the thread: "I've detected you have Claude Code / Claude Desktop installed, which probably indicates you have an Anthropic account — would you like to connect this app to that account to use the AI assistant features? Greatly enhances how this tool works." A proactive, detection-driven prompt turns "AI is off until you go configure it" into a one-click opt-in.
Proposal: On first run (or when no AI provider is configured), detect signs that the user already has a relevant account/tooling installed and offer to connect:
Detection should be cheap and privacy-respecting: look for the apps' presence (install registry entries / well-known paths / CLI on PATH) — do not read their credentials or config secrets. The prompt is just an onboarding nudge that routes the user into the appropriate connect flow.
Depends on / relates to:
Keep it dismissible and non-nagging (offer once; respect "no").