# Troubleshooting

When a result misses the mark, preserve the useful context, identify the failure precisely, and retry with a narrower instruction.

## The answer seems wrong

Ask Neo to re-check the claim, show its sources, state assumptions, and compare alternative interpretations.

> Re-evaluate the second conclusion. Cite the exact evidence, separate fact from inference, and explain what evidence would disprove it.

Provide missing context or an authoritative source if the issue came from ambiguity.

## The answer is too generic

Add audience, purpose, constraints, and examples. Ask for decisions tied to your actual inputs rather than general advice.

> Apply this to the attached policy and our 20-person support team. Give three concrete changes, owners, and risks.

## The result is too long

Specify priority and format:

> Lead with a five-bullet summary. Move evidence into a table and omit background the audience already knows.

## Neo keeps misunderstanding the request

Restate the current goal and source of truth in a clean message. Correct the specific assumption and ask Neo to repeat the revised scope before continuing. If the conversation contains unrelated or outdated context, start a new one.

## The task stopped early

Ask for a status summary, completed steps, blockers, changed files, and a restart plan. For large work, reduce the scope or use milestones.

## A file was not changed

Ask Neo to inspect the exact path and permissions, confirm whether editing is allowed, and show the proposed change before retrying. Check whether the file is generated, read-only, or outside the available workspace.

## A generated file is broken

Ask for the validation result and exact error. Confirm the file type, schema, encoding, and intended application. Preserve the original and recreate a minimal output before adding complex formatting.

## A web source cannot be opened

Provide another public URL, upload or paste the relevant content, or ask Neo to find an authoritative alternative. Treat inaccessible material as unverified.

## Citations do not support the claim

Ask Neo to remove or qualify the claim, locate the primary source, and quote the relevant passage with context. Always open critical citations yourself.

## A reminder is unclear or wrong

Specify the absolute date, exact time, timezone, recurrence, and message. Inspect the recorded schedule after creation and disable incorrect recurring tasks.

## A message may have gone to the wrong person

Stop further sending, inspect the connected service's status, and follow your organization's incident process. Do not assume a submission can be recalled. Verify recipients independently.

## A tool or capability is unavailable

Ask for the practical fallback: paste content, upload a file, provide a URL, create the final artifact manually, or perform the external action yourself. Availability can differ by account, workspace, and permissions.

## The reported work cannot be verified

Ask for direct evidence: file locations, a diff, tool result, test output, service status, or a reproducible check. A narrative summary is not proof that the action occurred.