fix(editor): stop highlighting start.input as blue when block is not connected to starter

[waleedlatif1]

Summary

• Removed start from hardcoded system prefixes that always highlight as blue
• <start.input> now only highlights blue when the block is actually connected to the starter block via edges
• loop, parallel, and variable remain as system prefixes since they are contextual constructs handled differently

Type of Change

• Bug fix

Testing

Tested manually

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Apr 8, 2026 7:47pm

[cursor]

PR Summary

Low Risk
Low risk UI-only behavior change that narrows when start.* references are syntax-highlighted; minimal surface area but could affect users who relied on unconditional highlighting.

Overview
Fixes reference highlighting so <start.*> is no longer treated as a hardcoded “system” prefix.

This removes start from the system prefix sets used by formatDisplayText and SYSTEM_REFERENCE_PREFIXES, meaning start references now only highlight when allowed by the contextual accessiblePrefixes (while loop, parallel, and variable remain always-highlighted).

^{Reviewed by Cursor Bugbot for commit 4940abc. Configure here.}

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[greptile-apps]

Greptile Summary

This PR fixes a UI highlighting bug where <start.input> references were always rendered in blue regardless of whether the block was actually connected to the starter block. It removes 'start' from the hardcoded system prefix sets in both formatted-text.tsx and references.ts, so the highlighting now relies on the edge-based accessiblePrefixes check — consistent with how all other non-system block references are resolved. The fix is correct because the starter block's name normalises to 'start' (via getUniqueBlockName), so it naturally appears in accessiblePrefixes when it is a true ancestor.

Confidence Score: 5/5

Safe to merge — a minimal, well-scoped change that correctly moves start from a hardcoded system prefix to the edge-driven accessibility check.

Both changed lines are simple set literal updates; all downstream consumers already fall through to accessiblePrefixes when the system-prefix check fails, and the starter block's name normalises to 'start' ensuring continuity when connected. The only finding is a P2 style suggestion about a duplicated constant.

No files require special attention.

Vulnerabilities

No security concerns identified.

Important Files Changed

Filename	Overview
apps/sim/app/workspace/[workspaceId]/w/[workflowId]/components/panel/components/editor/components/sub-block/components/formatted-text.tsx	Removes start from the local SYSTEM_PREFIXES set so <start.input> only highlights when the starter block is an actual ancestor; logically correct but maintains a duplicated constant instead of importing from the canonical source.
apps/sim/lib/workflows/sanitization/references.ts	Removes start from SYSTEM_REFERENCE_PREFIXES; all consumers that check this set fall through to accessiblePrefixes.has(normalizedPrefix), which will include start when the starter block (name "Start") is a real ancestor, so the fix is consistent.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["Reference token detected"] --> B{highlightAll?}
    B -- Yes --> H[Highlight blue]
    B -- No --> C{"prefix in SYSTEM_PREFIXES?\nloop / parallel / variable"}
    C -- Yes --> H
    C -- No --> D{prefix in accessiblePrefixes?}
    D -- Yes --> H
    D -- No --> E[No highlight / plain text]

    F["useAccessibleReferencePrefixes()"] --> G{Starter block\nan ancestor via edges?}
    G -- Yes --> I["normalizeName = 'start'\nadded to accessiblePrefixes"]
    G -- No --> J["'start' absent from accessiblePrefixes"]
    I --> D
    J --> D

Loading

_{Reviews (1): Last reviewed commit: "fix(editor): stop highlighting start.inp..." | Re-trigger Greptile}

[greptile-apps]

Duplicated constant diverges from canonical source

SYSTEM_PREFIXES here is a local copy of SYSTEM_REFERENCE_PREFIXES from references.ts — this PR keeps them in sync, but they can drift again with future changes. Since splitReferenceSegment is already imported from that module, importing SYSTEM_REFERENCE_PREFIXES directly removes the duplication.

Suggested change

	const SYSTEM_PREFIXES = new Set(['loop', 'parallel', 'variable'])
	import { splitReferenceSegment, SYSTEM_REFERENCE_PREFIXES as SYSTEM_PREFIXES } from '@/lib/workflows/sanitization/references'

Then delete the local const SYSTEM_PREFIXES = new Set(...) declaration entirely.

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 4940abc. Configure here.}