remotion-dev/remotion · error · Error

Guide ${guideId} not found in the current composition.

Error message

Guide ${guideId} not found in the current composition.

What it means

The remove-guide tool checks guidesListRef for a guide with the given ID belonging to the current composition; not finding one throws this error.

Source

Thrown at packages/studio/src/components/WebMcp.tsx:1479

						additionalProperties: false,
					},
					annotations: {readOnlyHint: false},
					execute: ({guideId}) => {
						if (typeof guideId !== 'string' || guideId.length === 0) {
							throw new Error('guideId must be a non-empty string.');
						}

						const compositionId = currentCompositionRef.current;
						if (compositionId === null) {
							throw new Error('No composition is currently selected.');
						}

						const guideExists = guidesListRef.current.some(
							(guide) =>
								guide.id === guideId && guide.compositionId === compositionId,
						);
						if (!guideExists) {
							throw new Error(
								`Guide ${guideId} not found in the current composition.`,
							);
						}

						const nextGuides = guidesListRef.current.filter(
							(guide) =>
								guide.id !== guideId || guide.compositionId !== compositionId,
						);
						guidesListRef.current = nextGuides;
						setGuidesList(() => nextGuides);
						persistGuidesList(nextGuides);

						const removedGuideWasSelected = selectedItemsRef.current.some(
							(item) => item.type === 'guide' && item.guideId === guideId,
						);
						if (removedGuideWasSelected) {
							clearSelection();
						}

View on GitHub (pinned to b2f4e34732)

Solutions

1. List guides for the current composition first and use a current ID

const guides = await listGuidesTool();
const exists = guides.some((g) => g.id === guideId);
if (!exists) throw new Error('guide not found');

When it happens

Trigger: Passing a stale guide ID from another composition, a deleted guide, or a made-up ID.

Common situations: Agents caching guide IDs across composition switches or after guides were already removed.

Understand the failure class

Background: "Not found" and "does not exist" errors: why "Task not found", "No such folder", and "Can't find" fire when a lookup comes back empty — this error's family across 14 libraries.

Related errors

• sequenceId must be a non-empty string.
• orientation must be either "horizontal" or "vertical".
• position must be a finite number.
• guideId must be a non-empty string.
• Job is not running

AI-assisted analysis of remotion-dev/remotion@b2f4e34732 (2026-08-28). Data as JSON: /api/errors/cfe17ba1f3ca964d. Report an issue: GitHub.