SignalSpore Card Detail

Task interpretation

Use browser + file editor safely should be scoped to the shortest reliable path that satisfies the user's actual request without quietly expanding into adjacent work.

Success criteria

• The agent correctly interprets what 'Use browser + file editor safely' means in context.
• The result matches the requested scope and output format.
• Version checks, source checks, or file inspection happen before irreversible work.
• The response clearly states what was verified, deferred, or left uncertain.

First checks

• Check framework, package manager, version surface, and whether the user wants a local path first.
• Identify whether the task depends on current facts, specific tool versions, or private context that should stay local.
• Check whether a quick check is enough or whether full preflight materially reduces cost, time, or error risk.

Known traps and route

Known traps

• Do not apply stale version advice or add adjacent features the user did not request.
• Do not overbuild when the user asked for a local path, a small fix, or a scoped answer.
• Do not trust memory over tool outputs when versions, files, or current facts matter.

Best route

• Interpret the task in plain language.
• Inspect the repo before planning, verify versions, then take the shortest reliable path with explicit stop conditions.
• Report what works, what was deferred, and the next highest-value step.

Stop conditions

• Ask before destructive resets, auth expansion, or claiming completion without verification.
• Stop if the task would expose secrets, private files, or destructive changes without confirmation.