6 / 7

Troubleshooting

Applies to the current Howse beta

Startup checks after an update

Howse 0.40.0 discards an earlier successful workspace check when the window reloads or the renderer fails. During a local app replacement, the old app backup is removed only after the newly installed app answers a fresh workspace check. If the current window is not ready, the backup is kept for recovery.

The app takes a long time to open

On Mac, update to Howse 0.30.0 or later if the window takes a long time to appear. This release reduces repeated recovery work for completed context records and improves startup scanning. Startup time still depends on the amount of stored data and your environment.

Core updates take effect on the next app launch. Wait for active work to finish before restarting; you do not need to delete your data or context records.

An agent won't run

Stopping and retrying

ToUseResult
Stop everything in a threadStop all (in the Manage list)Stops runs, pending waits, and follow-up work in this thread. Other threads keep going.
Stop one taskStop task (in the run bar or the Manage list)Stops that task and any runs that came from it.
Retry a failed runRetry in same session or Retry in new sessionCreates one new run of the same task. A new session replaces only that task's session.
Clear a failure from the listDismissRemoves it from the needs-attention list. Nothing is deleted.

Failed turns are managed in the run list without a duplicate interrupted card in the conversation. Acknowledged older error cards are hidden. A normally finished turn can complete silently when its final response is empty, without an extra provider run or a generated message. An explicitly empty Codex final response does not reuse earlier progress text as the final result. Acknowledged errors are also hidden in run details.

Did my message arrive?

In the channel list, reactions show each participating agent’s latest run in the thread, including retries and continuations. A completed continuation updates that agent’s channel reaction to ✔️. Reactions inside the thread still describe the individual message.

What happens when I quit?

Where are my data and logs?

Port conflicts

Howse runs a local server inside the app and binds it only to 127.0.0.1.

Recovery and run controls in 0.46.0

Update manually and restart after current work finishes if an orphaned question record prevents startup or an orphaned pending item causes Stop all to fail. This release skips those missing-message records without deleting your data. An already open stop/retry confirmation also follows the current execution lock. Empty or omitted optional Codex instructions no longer fail native validation.