Java Control points on Maven Central & a shorter initialise
Initialise now wires Java services to the ai.fireweave SDK on Maven Central, so a JVM surface can evaluate Fireweave Control points in production the same way TypeScript and Python already do.
Java joins the Control points path
A Java service initialised this week binds ai.fireweave:fireweave-sdk from Maven Central. Same shape as Python: Fireweave.init in local mode for development, remote mode for production — one call, one enum apart. Kotlin stays out of this surface for now.
A shorter initialise
Initialise no longer asks you to wire a boot beacon. Credential provisioning is framed as runtime keys — declining it continues the run instead of parking.
Fixed
- The same GitHub repo binds regardless of owner or name casing
- Project repo listings show the live serving connection
- Marketplace connection counts read the connections you actually have