Troubleshooting

When something does not look right.

When something does not look right, look for it here. Each answer says only what Ramble does, so if yours isn't here, email hello@kiruna.ai.

Recording

"Ramble can't hear you"

Your browser blocked the microphone. Ramble needs it, because your narration is the whole point. Allow the microphone for ramble.sh in your browser's site settings and start again.

While you record, each thing you say lands on the Ramble tab as its own line. If no lines appear while you talk, the microphone isn't picking you up.

"This browser can't save a compatible recording"

Ramble needs screen sharing and a WebM recording from the browser. Use a current desktop Chrome, Edge or Firefox.

You have used the free rambles a browser gets without an account. Sign in and keep going. The rambles you already recorded come with you. See Recording.

My mouse pointer isn't in the recording

Sharing a single window usually hides the pointer. Share your whole screen if you want it visible.

The recording stopped on its own

A ramble ends at ten minutes. It also ends if you stop sharing from your browser's own "Stop sharing" bar.

The home page shows "Unfinished recording"

The last piece of video didn't finish uploading, for example because the tab closed. Open Ramble in the same browser and press Resume saving to upload what is missing, or Delete local copy.

Your ramble

"Taking longer than usual"

While Ramble reads a recording, the page shows how long it has been working. A recording is usually done in under three minutes, and an uploaded video in one to five. Past that, the page says "Taking longer than usual. It will finish or say why." You can leave the page and come back. If grading stops making progress, Ramble marks the ramble failed and shows Retry.

The ramble failed

The page says why in a sentence, and shows Retry unless there is nothing Retry could do. For a recording it reads, for example, "The recording and transcript are safe. Press Retry to run the extraction pass again." Retry doesn't ask you to record again. See Your ramble.

The screen recording came out black

Some windows are recorded black on purpose, such as private or Incognito browser tabs, banking apps and protected video. When most of a recording is black, a notice above the findings says how long the screen was black and from when. Findings from that stretch rest on what you said and have no screenshot.

To get screenshots, share a different window, or your whole screen, and record again.

There are no findings

The page explains why in plain words. Common reasons are that nobody described a problem, that the screen was black for most of the recording, or that Ramble's reading did not finish. Retry shows when running it again could change the result.

"Findings may be incomplete"

Ramble's answer about the recording was cut off, and only the findings it had finished writing were kept. Anything it had not reached is missing. Retry reads the recording again.

I can't delete, edit or reorder this ramble

A ramble recorded while signed in belongs to that account, and only the owner can change it. Anyone else with the link can view it. They see no edit, remove, reorder or delete controls, and the page says "Only the owner can edit this ramble." Sign in as the owner. See Sharing and who can change what.

The page says some video is missing

Some pieces of the video never made it into the saved file, and playback may skip or glitch briefly where one is missing. The page says how many pieces arrived.

ChatGPT or another chat assistant can't open my ramble link

A chat assistant's web tool can only read pages it has already fetched and stored. A ramble link is private, so the assistant has nothing stored for it and reports that it can't open the page. This is expected, and sending the link again won't change it.

Two things work. Press Copy as text on the ramble page (Copy text in the phone app) and paste the result into the chat. It is the same plain-text document a coding agent reads, and it works in ChatGPT, Claude, Gemini or any chat. Or, if the assistant supports MCP, connect it so it reads the ramble itself. See Coding agents and the MCP reference.

Uploads

"That file is … MB. The limit is … MB."

The upload is over the size limit, which is 250 MB by default. The page names the limit it uses. Trim or compress the video and try again.

"That video has no audio track"

A ramble is narration, so a video with no sound has nothing to read. Record again with the microphone on, or add a voice-over.

"Ramble could not read that video file"

Export the video again, for example as an MP4, and upload that.

"The upload didn't arrive in one piece"

Nothing was kept. Upload it again. See Uploading a video.

Coding agents

My agent says "Needs authentication", or the ramble tools are missing

The connection is added but not signed in yet. Sign in from your agent:

Claude Code: run /mcp, choose ramble, choose Authenticate, finish in the browser, then run /ramble again.
Codex: run codex mcp login ramble.
Gemini CLI: run /mcp auth ramble.
Other agents: find ramble in the agent's MCP settings and sign in. If the agent has no browser sign-in, use a personal token.

`/ramble` is not a command

The skill isn't installed. Check that ~/.claude/skills/ramble/SKILL.md exists, or ~/.agents/skills/ramble/SKILL.md for other agents, then start a new session. Coding agents has the install commands.

`/ramble` lists no rambles

Most likely the agent is signed in as a different account. Ask it who it is connected as (ramble_find with view: "me" shows the email). Or the rambles were recorded while signed out, in a browser you haven't signed in with yet, or before Ramble tracked browsers. See Account.

"held by …"

Another session has claimed that finding. The claim lets go by itself when it runs out, or you can release it with Release on the ramble page.

"not_claimed" when setting a status

The agent's claim ran out while it waited for you. It needs to claim the finding again.

"insufficient_scope", or a 403

The connection tried something only your web sign-in, the phone app or Ramble for Mac may do, such as uploading, recording or deleting. Agents can't do those on purpose.

My agent says it can't switch to act

That is on purpose. An agent can set plan first, but only you can choose Act after posting the plan, under How agents proceed in Connected agents on Your rambles. See Plan first or act.

The wait for a recording keeps coming back "open"

That is normal. The wait (ramble_read with a request id) lasts up to 40 seconds each time. The agent calls it again until the request is answered.

An agent's access lasts 24 hours and renews itself while the agent is used. If the agent sits unused for 90 days, it has to sign in again. Two sessions that share one stored sign-in and refresh at the same moment can also sign each other out. Authenticate the agent again.

"That request from your coding agent isn't available any more"

The request has expired (60 minutes by default), been cancelled, already been answered, or belongs to another account. Ask your agent for a new one. Make sure you are signed in to the same account as the agent.

My agent asked me to paste a token into the chat

Don't. The /ramble skill never asks for one. If you made a personal token, keep it in your own terminal or config.

Ramble for Mac

The hotkey does nothing

If macOS or another app already uses ⌥⇧R, the popover says so under the switch. Check that the switch is on. See The hotkey. On a US keyboard layout the shortcut types "‰", so with the switch on that character can't be typed.

A link from my agent did nothing

macOS hands ramble:// links only to the installed Ramble app. Check that it is installed, running and signed in. If the popover opened on Sign in, sign in and ask your agent to try again. Or ask it for the web link. See Links from your agent.

The island says "That request has expired or isn't yours"

The same causes as above. The request is gone, or it belongs to another account.

Ramble for Mac asks me to relaunch

macOS applies the Screen Recording permission only to a new process. Press Relaunch and it is done.