good suggestion, adding to the next release

we are working with this consumer electronics company debug their zephyr project right now, would be worth trying out. if it doesn't work, email founders@embedder.dev we'll help you out

you can upload the esp32 docs to your own project, but we are working with espressif to have first party support for the docs baked in

exposing the context layer as an MCP is a very interesting idea that I did not consider; could be a good way to drive adoption. great suggestion.

Not just the context layer: the hardware interaction layer would be incredibly useful as a local MCP. These seem to be your special sauce, not the UI. Allowing users to access these from their preferred editors or cli tools would probably help adoption a lot.

Great work building this. If I was still in the hardware space I'd be all over this.

interesting, would you be open to chatting?

Happy to! I'll email your founders address tomorrow.

post cannot be edited, unfortunately...

thanks for the dev kit :)

We just edited it for you. Hope it's OK.

awesome!!

we are talking to a some of the larger vendors about getting first-party support for documentation. once we scale up a bit I think it could make sense to have multiple fine tuned models based on the docs they provide (or we crawl the web for public ones, at minimum)

there are some other companies trying to solve for PCB design. long term we want to build end-to-end AI automation for those cross-domain projects. this was a good place to start based on our personal/work experience

we store the files you upload for indexing

we don't store generated code / data, but it does pass through our API to the model provider. we store the usage meta data for billing purposes

strict grounding protocol + planning phase, mostly by prompting and forcing attention through citations. it tends to think longer than other coding agents but the results are usually better. let me know what you think.