Skip to main content
Engineers fixing the machine, not the repo

The Raycast diagnostic stack

Raycast grabs the error on screen, Perplexity cites the workaround, Notion files the runbook. Not Aider in git.

Who owns what

  1. Raycast AI

    The grab — window, clipboard, local shell/MCP. Not the wiki and not git.

    Try Raycast AI (opens in a new tab)
  2. Perplexity AI

    The cite — issues, breaking changes. Not OCR and not the shell.

    Try Perplexity AI (opens in a new tab)
  3. Notion AI

    The runbook page — trace, fix, next time. Not the hotkey.

    Try Notion AI (opens in a new tab)

How to use this stack

  1. Hotkey in Raycast. Capture the terminal or dialog. Do not paste into Cursor first.
  2. Perplexity gets the error string only — not your repo.
  3. Raycast applies the local fix if it is a tool or env issue. Then dump the note to Notion.
  4. This is not terminal-autonomous-coding. Not cursor-astgrep. The artifact is a runbook, not a commit.