Troubleshooting

Most problems fall into three groups: a model is offline, the conversation has outgrown its context window, or the browser is holding a stale copy of the app. Here is how to tell which.

“Model is not available right now”

The model server is unreachable. Models run on Rootcomputer's own hardware and go offline for training, maintenance, and power cuts.

• Switch models. They run independently — if Epos 2.1 is down, Epos 1.3 or Haiku H2 may be fine.
• Check the status page. It shows live health for every service plus any active incident.
• Wait and retry. Most outages are short. Your conversation is safe in the meantime — it is stored locally and does not depend on the server.

A reply failed or came back as an error

Use the Retry button under the failed message. This resends the same prompt without you having to retype it. If retry fails repeatedly, the model is probably down rather than the request being at fault — check the status page.

The model forgot something I told it

Almost always the context window. Each model can only hold so much conversation: about 32,000 tokens for Epos, about 1,000 for Haiku H2. Past that, the oldest turns are dropped silently.

• Watch for the context warning — it fires before truncation starts.
• Start a new chat for a new topic rather than continuing indefinitely.
• Branch from an early message to keep the setup while shedding the bulk.
• Restate the important detail rather than assuming it is still in range.

“Your message was not processed”

The message went over the model's word limit — 2,048 words on Epos, 200 on Haiku H2. The notice gives both the limit and your actual count. Nothing was sent and nothing was truncated; shorten it and try again, or switch to an Epos model if you are on H2.

Remember that pasted attachments count toward the total. If the number looks higher than what you typed, check the paste tray above the composer and remove anything you no longer need.

Web search problems

• No web search button. The model does not support it. Switch to an Epos model.
• Clicking it says web search is turned off. Re-enable it in Settings → Retrieval.
• It turned itself off after one message. Expected — it arms one message at a time. Click it again.
• The reply ignored the web. Check the disclosure line above the reply. If there is none, no search ran; if there is, the model read the pages but may not have used them well.

Replies are poor, short, or repetitive

• Too short? Switch effort to Extended (Epos models only).
• Too rigid? Move from Logical toward Casual.
• Inventing things? Move from Creative toward Logical. Creative widens sampling and a small model will confabulate fluently on that setting.
• Stilted deliberation on simple questions? Turn off force thinking.
• Worse after enabling augmented thinking? Turn it off — it is experimental and can misread a prompt.
• Missing recent information? Arm web search for that message, or check that Document retrieval is on in Settings → Retrieval.
• Still poor? Try Epos 2.1. The smaller models are genuinely much weaker, by design.

See Response controls for what each setting does.

My conversations are gone

Conversations live in your browser, tied to one device, one browser, and one profile. They will appear to vanish if you cleared browsing data, used a private window, switched browser or device, or have an extension that clears site data. Reaching the 256-conversation cap also drops the oldest.

The interface looks broken or half-updated

Usually a caching problem: the browser has an old stylesheet paired with a new script, or the reverse. A hard refresh fixes it — Ctrl + Shift + R, or ⌘ + Shift + R on a Mac. If that does not work, clear the site's cached files.

Audio problems

• Nothing plays on first press. Browsers block audio until you have interacted with the page. Press again.
• The spinner never finishes. The speech service may be down — check the status page.
• No microphone button. Your browser does not support speech recognition. Chrome and Edge do; Firefox generally does not.
• Dictation does nothing. Either the Microphone switch is off in Settings → Privacy, or your browser has denied permission. The button says which.
• No waveform on Android. Expected — the system speech service takes the microphone exclusively. Dictation still works.
• Silent on iPhone. Check the hardware mute switch, which silences web audio separately from volume.

Layout problems on mobile

If the layout looks wrong after the address bar shows or hides, rotating the device or scrolling usually settles it. If the keyboard covers the composer, collapsing and reopening it forces a relayout.

Reporting a problem

For a bad reply, the thumbs down button with a note about what should have been different is the most useful report you can file — it goes directly into the training data. Note that this uploads the exchange; see Your data and privacy.

For a broken interface or an outage, check the status page first — incidents are detected and posted automatically, so a known problem is often already listed.