RunHuddleAn agent is missing
Install and authenticate its CLI, then open Settings → Connections. Check the exact error and tracking status. Finder-launched apps may not inherit a custom shell environment. See Agent connections for provider-specific setup.
An agent behaves differently from a regular terminal
RunHuddle 0.36.2 starts new and resumed agent processes through your macOS account’s login shell in interactive mode. This loads the shell’s normal startup files, including .zshrc for zsh. Existing processes retain the environment they started with; reattaching a terminal or restarting RunHuddle does not reload it.
After updating, exit the affected agent and resume its saved conversation to pick up the corrected startup environment. RunHuddle does not add flags that bypass or disable agent approvals. Browser integrations also require the agent’s own connector and permission setup; filesystem access alone does not grant browser access.
A conversation is visible but I cannot type
A recorded conversation is not a live embedded terminal. Sessions running outside RunHuddle remain read-only here. Exit the original agent, wait for status reconciliation and choose Resume this session. New sessions launched from RunHuddle use the embedded terminal directly.
Do not install old reply extensions or enable development channels for the current workspace. Those instructions describe a retired workflow.
A closed session still appears active
Use View → Refresh session data. Agent shutdown can take time, and the fallback reconciliation runs about every 30 seconds. A shared or background session may still be alive. Codex’s normal unload delay can make End and archive wait about a minute before closure is confirmed.
If another client is attached, stop or detach it intentionally. Do not bypass liveness checks or repeatedly launch the same conversation.
Hooks mention an old app location
Keep one installed app at its permanent location. Check Connections for RunHuddle’s path repair and retry controls. Fully exit and relaunch affected Claude/Copilot processes to load updated hooks. Claude /resume inside an already-running process may retain old hook commands. Unrelated hook settings should remain untouched.
I cannot see the session list or info panel
Use the two pane buttons above the workspace, ⌘⇧L for the list or ⌘⇧I for Session info. Resize the window if necessary. Closing a Project changes tab returns to the session; hiding a pane does not stop the terminal.
No checklist or context percentage appears
These require supported evidence from the agent. Plain-text checklists are not structured plans. Unknown context usage is not shown as zero, and an absent checklist does not imply idle status. Large transcripts can take several refreshes to scan.
Notifications do not appear
Check Settings → Notifications, quiet hours, snooze and muted projects. Use the test alert. Also check macOS notification permission and Focus settings. See Inbox and notifications for grouping and reminder behavior.
Colors or shortcuts look wrong
Check Settings → Appearance and Terminal. Agents may set explicit RGB colors or cursor shapes independently of the theme. Review Option-as-Meta and CLI-specific shortcuts before resetting preferences. You can restore a preset without deleting saved themes.
Handoff or note generation fails
Check the selected provider’s sign-in, allowance and account restrictions. Generation can time out or fail without changing an existing draft. Retry after resolving the provider error. Review output before saving or launching; source history may be incomplete.
Updates or duplicate copies
Use Check for Updates…, or replace the installed app in the same location. Avoid launching a checkout’s development app alongside the installed copy. A newer development workspace may differ from the current public release.
Report an issue
Use GitHub issues. Include the RunHuddle version from About RunHuddle, macOS and CLI versions, steps to reproduce and the relevant error. Remove private text and credentials from screenshots and logs. For developer build problems, use the build guide.