Context and mentions¶
Hydron discovers relevant C/C++ files on demand using built-in search tools. For firmware work where strict boundaries matter, use @-mentions to anchor the agent to specific files or commits.
Type @ in the chat input to open the autocomplete menu.
| Mention | Attaches | Firmware use case |
|---|---|---|
@file | A local file's contents | "Add DMA support to @src/drivers/drv8316.c." |
@git-changes | Uncommitted diffs | "Write a commit message for @git-changes." |
@commit-hash | A specific commit | "Did @a1b2c3d introduce this priority inversion?" |
Drag and drop¶
In VS Code, drag files from the Explorer directly into the chat pane. Hold Shift to drop external images such as schematic snippets or logic analyser screenshots for visual analysis.
Trust the discovery tools¶
Mentions are for precision, not for everything. For sweeping architectural questions such as "find everywhere we use blocking delays in ISRs", just ask. Hydron's internal search covers it faster than tagging every header by hand.
Reach for a mention when the answer depends on one specific file and the wrong one would be plausible.
Trigger datasource lookup¶
Mentions anchor local files. To pull from your attached datasheets and specifications, use trigger words in the prompt: query, refer to, look up, or naming the project.
Without them, Hydron may answer from training data rather than your attached documentation. See Best practices.
Next¶
- Datasources for what Hydron can reference.
- Best practices for anchoring context effectively.