NeurionTools & context
Context & long tasks
Keep important requirements and sources available throughout a task.
HydraLabs · Published
Supply the context the task needs
Include the relevant files, examples, constraints, and acceptance criteria. Project instructions and enabled skills guide the work alongside your messages. Selecting a project does not copy every file into every model request.
For large documents, ask a focused question or identify the section that matters. For repository work, identify the feature or failure rather than attaching a complete unrelated codebase.
Keep exact requirements in a project document or another persistent file when later steps must refer to them precisely.
Understand automatic compaction
As a conversation grows, Neurion summarizes older material to make room for ongoing work. Current task state, critical instructions, and relevant references are carried forward. There is no manual compaction step to perform.
A summary is not an exact transcript. Restate a detail or point to its source when exact wording, a number, or a previous decision is important to the next step.
If the task resumes after a long interruption, confirm its objective, current state, and remaining work before asking for a consequential action.
Separate saved history from working context
Saved conversation history and the model’s current working context are different. Reopening a conversation preserves access to its history; it does not send every earlier message verbatim on the next request.
Large attachments are stored and processed locally for retrieval. Relevant passages or image content enter AI requests when the task uses them. Local storage does not mean that selected content is never processed in the cloud.
A fork creates a separate continuation. Independent conversations do not share a universal memory of every local project or past decision.
Use sources and check coverage
Neurion can search the scoped project and retrieve passages from attached documents. Search results are selected evidence, not automatic proof that the entire project or document was read.
For a complete document summary, request complete coverage and review any extraction or coverage limits. A missing search match does not establish that a document has no relevant answer.
After an interruption, inspect the latest task state, files, and outputs. Do not treat an operation without a confirmed result as completed.