Upcoming Features

v0.2 — Devtools Browser Extension

Expected: Q3 2026

A browser extension that makes the AI contract visible and inspectable during development. Every CortexUI app gains a live overlay showing the machine-readable contract as it exists in the DOM.

Features:

• Visual badge overlay — Every element with data-ai-* attributes gets a badge showing its role and ID. Action elements are highlighted in blue, form fields in green, sections in gray. The overlay can be toggled without affecting the page.

• Contract tree panel — A DevTools panel that shows the full contract tree for the current screen: screen context at the top, sections, entities, and available actions in a structured tree. Click any node to inspect the full set of data-ai-* attributes on that element.

• Real-time event log — Live display of the CortexUI runtime event log. See every action_started, action_completed, and action_failed event as it fires, with full event payload. Filterable by action ID, event type, and section.

• Contract validation warnings — The extension validates the contract as it scans the DOM. Missing required attributes, invalid state values, duplicate IDs, and elements that appear interactive but lack contract annotations are flagged with inline warnings in the overlay and a summary in the DevTools panel.

v0.3 — Design-to-Contract Pipeline

Expected: Q4 2026

A Figma plugin that generates CortexUI contract annotations from design files, closing the gap between design and implementation.

Features:

• Component annotation in Figma — Designers can annotate components directly in Figma with their intended data-ai-action, data-ai-role, and entity context. Annotations are stored as component properties and exported with the design spec.

• Contract export in handoff — When a developer inspects a component in Figma, they see the AI contract alongside the visual spec: the action name, the valid states, the entity context. No back-and-forth required to establish the contract.

• Auto-suggestion from component names — The plugin analyzes component names and generates data-ai-action suggestions. A component named "Save Profile Button" gets the suggestion save-profile. Designers confirm or modify the suggestion.

• Design token sync — Design tokens defined in Figma variables are synced to the CortexUI token system, ensuring that visual and contract layers use a consistent vocabulary.

v0.4 — Native Agent SDK

Expected: Q1 2027

A TypeScript SDK that provides type-safe, ergonomic access to CortexUI apps from AI agents. Removes the need for manual page.evaluate() wrappers and provides built-in reliability patterns.

Features:

• Type-safe runtime access — Full TypeScript types for all window.__CORTEX_UI__ API responses. Autocomplete for action IDs, form field IDs, and event types in agents that import the SDK.

• Built-in retry and error handling — Configurable retry policies for action execution, automatic detection of transient failures versus permanent errors, and structured error types that carry the contract context.

• Action sequencing utilities — Higher-level primitives for common agent patterns: fillForm(), executeAndWait(), waitForState(), expectEvent(). Reduces boilerplate in agent implementations.

• Claude and GPT integration modules — Pre-built integration modules that format CortexUI context into the optimal prompt structure for Claude and GPT models, and parse model responses back into action IDs. Makes the "query contract → ask model → execute action" loop a one-liner.

v0.5 — Multi-agent Coordination

Expected: Q2 2027

Native support for multiple agents operating on the same UI simultaneously, with runtime-level coordination primitives.

Features:

• Action locking via data-ai-lock — An agent can claim an action before executing it. The runtime surfaces locked state in getAvailableActions() responses. Other agents see the lock and wait or route to alternative actions.

• Agent identity: data-ai-agent — Agents register with the runtime under an identity. When an agent interacts with an element, the element is tagged with data-ai-agent so other agents know it is in use. The agent identity is included in all emitted events.

• Conflict resolution primitives — Runtime-level detection of simultaneous interactions. Configurable resolution strategies: queue (second agent waits), fail-fast (second agent throws), merge (runtime merges compatible interactions).

• Agent coordination event types — New event types in the event log: action_claimed, action_released, agent_registered, agent_entered_section, agent_exited_section. Full audit trail of multi-agent sessions.

Contributing

CortexUI is open source and actively welcoming contributions. The highest-impact areas for community contribution:

Contract specification improvements — Proposed additions or refinements to the data-ai-* vocabulary. Open an issue on GitHub with a use case, proposed attribute name, valid values, and example markup.

New component implementations — CortexUI's component library is not exhaustive. Complex components like date pickers, rich text editors, drag-and-drop lists, and data grids have nuanced contract requirements and would benefit from community-contributed reference implementations.

Runtime extensions — The runtime is designed for extension via the customAttributes API and onCustomAttribute hook. Runtime extensions for specific domains (healthcare FHIR data, financial transaction workflows, e-commerce checkout) would benefit the community.

Framework adapters — CortexUI components are currently React-first. Vue, Svelte, Angular, and SolidJS adapters that expose the same contract primitives for other framework communities are high-value contributions.

Documentation — Additional examples, tutorials, and translated documentation lower the barrier to adoption. Documentation contributions are always welcome.

See CONTRIBUTING.md for contribution guidelines, development setup instructions, and the RFC process for specification changes.