Task won’t start
Task stuck on 'Setting up environment'
Task stuck on 'Setting up environment'
Task containers usually start within 60 seconds (up to 3 minutes for custom workspace images). If a task is stuck:
- Check your CU balance — you can’t start tasks with a depleted balance
- Check your active task limit — Free and Pro plans allow 20 active tasks; archive or complete old tasks to free up slots
- Try again — transient infrastructure issues occasionally delay container creation. Create a new task with the same prompt
- If the issue persists, check the Whim status page or contact support
Task fails immediately after starting
Task fails immediately after starting
This usually indicates a problem with the workspace image or environment:
- Custom workspace image build failure — check the image build logs in Settings → Workspace Images for errors
- Missing dependencies — ensure your workspace image includes the tools your task needs
- Repository access — verify the GitHub App is installed and has access to the repository
Terminal issues
Terminal not loading
Terminal not loading
If the terminal pane appears blank or shows a connection error:
- Refresh the page — this re-establishes the terminal connection
- Check your internet connection — the terminal requires a stable WebSocket connection
- Try a different browser — some browser extensions can interfere with WebSocket connections
- Disable VPN — some VPNs block WebSocket traffic
Terminal disconnecting frequently
Terminal disconnecting frequently
Brief disconnections are normal when switching tabs (especially on Safari). Whim automatically reconnects when you return. If disconnections are persistent:
- Check your network stability
- Ensure your browser tab isn’t being aggressively suspended (disable tab sleeping/discarding in browser settings)
- Try a wired connection instead of Wi-Fi
Git issues
Git push or pull fails
Git push or pull fails
Git operations require the GitHub App to be installed with the correct repository permissions:
- Go to Settings → GitHub and verify the GitHub App installation is active
- Ensure the app has access to the specific repository you’re working with
- If you recently changed repository permissions on GitHub, reconnect the integration in Whim settings
Branch conflicts
Branch conflicts
Each task runs on its own isolated branch. If you see merge conflicts when the task tries to push:
- The base branch may have been updated since the task started
- Fork the task to retry with a fresh branch based on the latest code
- Use the terminal to manually resolve conflicts if needed
AI provider issues
Provider connection errors
Provider connection errors
If an AI provider is unreachable:
- Check provider status — Anthropic, OpenAI, and OpenRouter each have their own status pages
- Try a different model — create a new task with an alternative provider
- Check CU balance — some provider errors occur when the CU balance is too low to cover the request
Agent seems stuck or unresponsive
Agent seems stuck or unresponsive
If the AI agent isn’t making progress:
- Send a follow-up prompt — sometimes the agent needs guidance to continue
- Check the terminal — the agent may be waiting for input or confirmation
- Fork the task — create a fresh attempt with a more specific prompt
- Whim detects stuck agents (idle for over 2 minutes) and can alert you via browser notifications
CU balance issues
CU balance seems wrong
CU balance seems wrong
Check your usage breakdown in Settings → Usage to see exactly which tasks consumed CUs. Remember:
- CUs combine container runtime and token usage — a task that ran for 10 minutes but processed many tokens can consume more CUs than expected
- Reserved machines consume 3 CU/week each
- CU periods reset weekly from your subscription anchor date, not on a fixed day
Can't start tasks despite having CU balance
Can't start tasks despite having CU balance
Check if you’ve hit your active task limit (20 for Free/Pro, 40+ for Max). Complete or archive finished tasks to free up slots.
Browser notifications
Not receiving notifications
Not receiving notifications
- Check Settings → Notifications — ensure the master toggle and relevant type toggles are on
- Check your browser permissions — you may have blocked notifications for whim.run
- Remember that notifications only fire when the Whim tab is not in focus
- On macOS, ensure notifications are enabled for your browser in System Settings → Notifications
Previously denied notification permission
Previously denied notification permission
Whim can’t re-prompt for notification permission once denied. To reset:
- Chrome: Click the lock icon in the address bar → Site settings → Notifications → Allow
- Firefox: Click the lock icon → Clear permission for notifications
- Safari: Safari → Settings → Websites → Notifications → find whim.run → Allow
Mobile
Limited functionality on mobile
Limited functionality on mobile
Whim is optimized for desktop browsers. On mobile devices:
- The terminal view may be difficult to interact with on small screens
- File drag-and-drop is not available — use the file picker instead
- Browser notifications may behave differently depending on your mobile OS

