NeurionGet started
Your first task
Give Neurion a clear goal, useful context, and a result you can verify.
HydraLabs · Published
Describe the outcome
State what you want to achieve, the relevant project or target, and any constraints. Explain how you will recognize a successful result. Include exact filenames, examples, or acceptance criteria when they matter.
A useful first request is: “Explain how this project starts, identify the entry points, and list its existing checks. Do not change files yet.” For a writing task, specify the audience, format, and source material.
Attach only the material needed for the task. Remove credentials and unrelated private content from examples you intend to share.
Choose model, mode, and permissions
Select Neurion Flash or Neurion Pro, then choose an effort level supported by that workflow. Use Planner for an approach, BugBot for a review or diagnosis, and CyberBot for an authorized security investigation.
Open the relevant project for code inspection. Review requested file access, commands, browser actions, and external targets. Adding one attachment does not grant access to every file on your device.
The task uses your workspace’s shared usage allowance. Higher effort, longer context, and delegated work increase the resources required.
Follow and steer the work
Use the visible progress and tool activity to understand what is running and whether an approval is waiting. A task can be working before its final response appears.
- Send a correction when the current task needs new direction.
- Queue a follow-up when it should wait until the current response is finished.
- Review approval requests against the exact target and effect shown.
- Use Stop to end the current work. Completed file changes and external actions are not undone by stopping.
If the application reports an uncertain result, inspect the existing operation before requesting a repeat. This is especially important for payments, publication, deletion, and other consequential actions.
Check what was completed
Read the final response, open its referenced files or findings, and inspect code changes. Check the reported validation and distinguish completed checks from recommended next steps.
For a repair, confirm that the original failure was retested. For research, follow the cited sources. For a generated artifact, open it in its intended viewer before relying on it.
Continue in the same conversation when the next step depends on its history. Start a separate conversation when the goal or working context is independent.