Main Menu

Announcing HYPER v0.9 - Building the Foundation for Agent-First Software

publish_icon

6 July, 2026

reading-minute-icon
5 minutes

Product Name: HYPER

Release Version: v0.9

Release Date: July 2026

Prepared By: HYPER Product Team

Licensed To: CodeNinja

Summary 

HYPER v0.9 delivers the core infrastructure for dual-architecture software systems: enterprise applications designed from the start for human operators and agent residents simultaneously. 

v0.8 made every HYPER-generated application MCP-ready and introduced the execution layer that transforms applications from static interfaces into operational systems. The Hyper for Claude release showed what those systems become when Claude operates them at the surface: domain experts running governance systems from inside Claude, engineering removed from the operational loop, every function exposed as an MCP tool the model can reason over and act on. 

v0.9 builds the infrastructure that makes this architecture scale across real enterprise complexity. The Requirement Agent expands into a structured planning mode capable of handling large, layered requirements before generation begins. HYPER Studio introduces deeper control across field configuration, authentication, navigation, and access management. Hyper AI extends beyond code generation into system configuration, capable of building automations, adjusting access control, managing menus, and modifying themes. Multi-language infrastructure makes generated systems ready for regional and global enterprise deployment from the first release. 

Three principles define this release. 

Agents as first-class residents 

Dual-architecture software does not retrofit agent access after the fact. It designs for agent and human interaction simultaneously from the first configuration decision. Every system generated by HYPER v0.9 is structured for both residents from the beginning, removing the architectural debt that accumulates when agent access is treated as an addition rather than a foundation. 

Business intent into software architecture 

Enterprise requirements do not arrive as clean specifications. They arrive as layered documents covering multiple teams, roles, workflows, permissions, dashboards, and integration points. Plan Mode in the Requirement Agent converts that complexity into structured planning phases the team can review and validate before a single line of code is generated. 

Governance at the configuration layer 

Authentication depth, role-based access foundations, and Studio control precision are architectural properties in v0.9, not engineering add-ons applied after deployment. Systems generated in this release are enterprise-ready and compliance-structured from the first build. 

Platform Modules and Features Delivered 

1. Requirement Agent Expanded to Plan Mode 

  • Structured Plan Mode breaks complex enterprise requirements into clear planning phases before generation begins 
  • Handles large, multi-team requirements covering roles, permissions, dashboards, integrations, and operational rules in one flow 
  • Teams review, refine, and validate the system plan before any code is generated 

Why this matters: Enterprise requirements are layered and difficult to translate directly into software architecture. Jumping from a product requirements document to generation introduces errors that compound through the build. Plan Mode places a structured review layer between business intent and architecture, giving teams the ability to correct the plan before it becomes code. This is the mechanism by which HYPER handles enterprise-scale complexity without sacrificing the speed of AI-assisted generation. 

2. Project Import, Export, Duplicate, Backup, and Restore 

  • Export, import, duplicate, backup, and restore across the full project lifecycle inside HYPER 
  • Projects become portable, reusable assets that move between environments and team configurations 
  • Hyper Sync integration is planned to extend project portability across deployments 

Why this matters: Enterprise delivery is not a one-time generation event. Teams reuse successful architectures, move projects between environments, and need to recover from changes safely. With project portability built in, HYPER-generated systems become reusable infrastructure rather than single-use outputs. Delivery speed improves because proven patterns carry forward rather than being rebuilt from the start. 

3. Studio Control Layer Improvements 

The core configuration layer inside HYPER Studio has been extended across field setup, collection options, authentication, navigation, subforms, related models, multi-language setup, and automation configuration. 

Include Controls 

  • Controls which related models and subforms appear on any given screen 
  • Replaces the default behavior of showing all related data or none of it 
  • Applied at the form and view level, not globally 

Why this matters: Enterprise records rarely stand alone. Forms and views need selected related data alongside the primary record, not every related object the system contains. Include Controls let teams decide, form by form, which related records belong on screen. Generated systems become accurate and implementation-ready rather than cluttered or incomplete. 

Navigation Builder 

  • Defines how users move across the application, which sections are visible, and how workflows are organized 
  • Navigation structure is configurable inside Studio without requiring code changes 

Why this matters: Navigation shapes daily system usage for every person working inside a generated application. Clear navigation makes enterprise applications understandable, operable, and ready for team-wide adoption from the first deployment. 

4. Multi-Language Configuration and i18n Support 

  • Multi-language configuration UI inside Studio 
  • Database-level multi-language support across generated applications 
  • React i18n support and improved frontend internationalization coverage 

Why this matters: Enterprise applications serve users across regions, departments, and languages. Localization that lives only at the UI level breaks when users interact with data at the configuration or database layer. With multi-language and i18n support running across all three layers, HYPER-generated systems are structurally ready for global clients, regional deployments, and multilingual internal operations without post-generation rework. 

5. Hyper AI Skills for System Configuration 

  • Automation Builder: generates automation flows from natural language instructions 
  • Area General Skill: updates area-level system settings through AI assistance 
  • ACL Skill: configures access control rules without manual screen navigation 
  • Menu Skill: manages navigation menus and section visibility 
  • Theme Skill: adjusts system appearance and visual configuration 

Why this matters: Hyper AI is moving from a generation assistant into a system configuration partner. Domain experts should not need to navigate complex configuration screens to define how their system behaves. With these skills, the same natural language interface used to generate applications extends to the configuration layer, reducing manual effort and moving HYPER closer to AI-operable software where the system configures itself in response to the team that owns it. 

6. Automation Module (Redesigned) 

  • Redesigned workflow creation experience using triggers, conditions, and actions in a structured flow 
  • Supports automated record updates, conditional logic, and external system integration 
  • Execution layer strengthened for AI-driven and agent-driven operational actions 

Why this matters: Enterprise systems should not only store and display data. They should execute work, reduce repetitive operations, and support the agent-driven actions that dual-architecture software requires. The redesigned Automation module makes workflow creation accessible to the teams building operational systems, not only to engineers who understand the underlying execution layer. This directly supports the Hyper for Claude model: agents need a reliable execution surface to act on, and the Automation module is where that surface is built. 

7. Enterprise Sign-In and RBAC Foundation 

  • Configurable sign-in methods: password sign-in, passwordless access, two-factor authentication, and social login 
  • Username fields, password fields, password rotation behavior, and user-level authentication rules configurable from Studio 
  • RBAC readiness through improved access configuration and the Deploy RBAC Seed action for role-based permission initialization 

Why this matters: Enterprise applications require secure identity flows, flexible sign-in methods, and role-based access from day one. Authentication requirements that are retrofitted after deployment create compliance risk and engineering debt. With authentication depth and RBAC foundations built into Studio configuration, HYPER-generated systems meet modern enterprise identity requirements from the first build, without manual engineering work on top of the generated output.

Vision and Road Ahead 

Next Release Theme: Sovereign AI 

The next release focuses on open-source infrastructure and freedom of technology. This means giving teams deeper control over the core technology that powers their systems of context, from foundation models and harnesses to infrastructure, execution layers, and agentic workflows. The direction is consistent with the architectural conviction that has defined HYPER since v0.8: the intelligence the platform produces belongs to the organization that built it, permanently and without qualification. 

Availability: 

HYPER v0.9 is now available to all existing partners and will be available to enterprise clients through three engagement models:  

Hyper Core: This annualized plan is built for enterprises with internal engineering capability, providing access to eight million lines of deterministic and compile-validated code per month to drive autonomous development. 

Hyper Synergy: This plan is engineered for organizations looking to accelerate delivery, combining full platform access with dedicated Forward Deployed Engineers embedded directly within the client team to guide architecture and implementation. 

Hyper Horizon: This plan is custom-scoped for large-scale enterprise transformation, designed specifically for organizations systematically replacing legacy SaaS dependency across multiple workstreams simultaneously.

Points of Contact 

Umar Khan, Product Manager

[email protected]

Huzaifa Zulfiqar, Senior Account Manager

[email protected]

Notes for Stakeholders 

v0.9 represents a significant step toward the dual-architecture model that defines HYPER's direction: software systems where agents and human operators share the same application foundation from the first line of code. The infrastructure introduced in this release, from Plan Mode in the Requirement Agent to enterprise authentication and Hyper AI configuration skills, is designed for systems that do not just store or display data, but act on it under agent direction. 

All prior v0.8 functionality remains active and enhanced. v0.9 builds on the MCP-ready architecture, execution layer, and governance foundation established in the previous release and extends each in the direction of enterprise production readiness.