Datasources¶
Datasources are the codebases and documents that define your hardware and software stack. Everything you add flows into every prompt you run across the CLI and the VS Code extension.
Codebases¶
Paste a GitHub repository URL, public or private. For private repositories, Hydron prompts you to authorise with a GitHub personal access token requiring repo scope.
You can also upload a zipped codebase to be indexed directly.
Tip
Keep the repository cloned locally as well. Hydron needs the files on disk to reference your active working directory and pick up uncommitted changes.
Files¶
Upload any artifact that defines your stack: datasheets, reference manuals, schematics, BOMs, application notes, or proprietary specifications.
| Format | Limit |
|---|---|
| GitHub repository | Up to 50 MB |
| Up to 100 MB, 5,000 pages | |
| Word, Excel, CSV, Markdown, XML, Text | Up to 500 MB each |
| ZIP | Up to 500 MB |
What to attach¶
Datasheets are the single biggest accuracy multiplier on firmware projects. Attach the datasheet for every chip your project drives.
- Attach errata sheets separately. They often contradict the main datasheet on edge cases, which is exactly where a wrong answer costs you a day.
- Re-attach when the vendor publishes a new revision. Datasources do not auto-update.
- Add your own board material even when the platform is catalogued. Schematics and internal specs make answers specific to your variant.
Scoping¶
Datasources are scoped to the project. Confirm the right project is selected in the CLI or VS Code before prompting, or Hydron answers without them.
Next¶
- Hardware Registry for pre-indexed components.
- Best practices for prompting against datasources.