Overview
When the open-source HazelJS core needs a product-specific extension, we design, build, and maintain packages that stay coherent with Agent OS patterns.
Who it is for
Product teams standardizing on HazelJS who need domain-specific capabilities beyond the core.
The problem
Forking the framework or scattering one-off glue makes upgrades and governance harder. Extensions should be packaged cleanly.
What you get
- Extension design aligned with Agent OS boundaries
- Typed packages or internal libraries
- Skillgate / capability curation where relevant
- Tests and usage docs for your engineers
- Upgrade-friendly packaging guidance
Technical scope
Custom packages, Skillgate capabilities, DNA overlays, and internal libraries that extend HazelJS Agent OS for your product surface — built to match your conventions and ownership model.
How we work
- 01
Identify the gap against open-source core
- 02
Design package boundaries
- 03
Implement and test
- 04
Integrate with your agent runtime
- 05
Document ownership and upgrade path
FAQ
- Will extensions be open-sourced?
- Only if you choose to. Many extensions remain private product IP.
- Can you contribute upstream to HazelJS?
- When a change belongs in the public core, we can help shape an upstream contribution. Product-specific logic usually stays in your packages.