# Troubleshooting

> A practical checklist for launch, permissions, models, agents, voice and extensions.

Start with one failing action and the exact message Redcast shows. Check the relevant setting before resetting data: many features are deliberately off until enabled.

## The launcher does not open

Use the menu bar item to open Settings. Record a shortcut in General; there is no default binding. Check [Shortcuts](/docs/reference/shortcuts-overview) for collisions and try a chord not used by another launcher. Make sure the installed Redcast and Tinycast Dev are not both claiming it.

## Pasting or window control fails

Check **System Settings → Privacy & Security → Accessibility**. After a certificate or bundle-ID change, a checked old entry may be stale. Add the current Redcast app and test a simple paste in TextEdit. Secure fields and apps that do not expose the needed Accessibility operation can still refuse.

## File search is empty

Enable File Search and grant Full Disk Access manually. Allow the initial private index to build, then check excluded locations and the search query. An agent's `search_files` uses Spotlight and is a different path from the launcher's index.

## AI reports an error

Check the provider is enabled, the selected model still exists, and the connection's key or sign-in is valid. Test a short text message before adding tools or attachments. A gateway may support chat while rejecting tools, images or audio. Use the error's named unsupported field or capability to narrow the problem.

For ChatGPT-plan sign-in, restart a timed-out browser flow and ensure the local callback can use port 4965. Do not copy another application's authentication file into Redcast.

## An agent does not perform an action

Inspect its tool row and permission refusal. Confirm its folder exists, the tool family is enabled and the route supports tool calling. Background runs may decline an asking operation when nobody is present. ACP agents also need a valid executable, their own login and an actual ACP transport.

## A schedule did not run

Redcast must be running. Check the schedule is enabled, its missed-run policy, the local time zone, whether its agent is busy, and its reported daily spend cap. Imported schedules start paused. A catch-up policy combines missed occurrences rather than replaying each one.

## Voice fails or inserts nothing

Check Microphone, Accessibility, the selected input device and the model's readiness. Cloud transcription also needs its approved audio connection. Inspect Dictation History for a failure and retry while its recording is still available. A successful retry updates the entry; paste it yourself.

## An extension opens but its command fails

Check required preferences and sign-in inside the extension. Confirm any package manager required by its installation path. Compare the command against [runtime limitations](/docs/extensions/compatibility). A Store listing does not certify compatibility with every Raycast API.

## A restored setup is partly off

This is expected for capability switches, imported MCP servers and schedules. Read the import summary and re-enable only what you intend to use. Sign in with ChatGPT again, reinstall extension bundles and repair agent paths missing on the new Mac.

## Report a reproducible bug

Open an [issue in Redcast's repository](https://github.com/alesha-pro/redcast/issues) with the version, macOS version, minimal steps, expected result and actual result. Name the model route or extension command when relevant. Include a redacted error or screenshot, not a dump of credentials or private histories.