Our own engineering — Harmonica
Bringing AI into the engineering workflow
Connecting model providers, engineering context, and tools inside Codazen’s delivery workflow.
Context
An engineering workflow carries context across plans, code, tools, and reviews. Connecting a model to only one of those surfaces leaves the rest of the work outside the application.
Approach
We treated model access as one part of the delivery workflow. The integration needed to connect engineering context and permitted tools, preserve session records, and support review of the resulting work.
Our role
Harmonica brings provider-specific model access into a shared application workflow. The surrounding integration connects the selected model to engineering context and tools, rather than requiring the engineer to recreate that context around each request.
Agent sessions capture their actions and results. Model-backed checks can examine plans and implementations, giving engineers another source of evidence to inspect during delivery.
- Model and application integration
- Engineering context and tool access
- Session records and review evidence
What this demonstrates
The work connects model access, application tools, session handling, and review evidence inside an existing engineering process.
Explore the engineering
Forward-Deployed Engineering
Bring experienced engineers into the systems and workflows where the challenge lives.
Explore Forward-Deployed EngineeringMore work
Our own engineering — Harmonica
Connecting Meta models to an existing application
Integrating hosted Meta model access with chat, tools, session records, and application controls.
Read case studyOur own engineering — Harmonica
Giving an engineering agent the context and tools to work
Integrating the Claude Agent SDK with engineering tools, workspace access, and resumable sessions.
Read case studyLet’s put your next priority into production.
Tell us about the workflow, integration, or delivery challenge your team needs to move forward.
Discuss your next priority