React

In Helix I wanted people, and the AI colleague they work with, to stay inside the platforms they already use. I build front ends as integration surfaces inside other people's platforms: small, native-looking and backed by a server-side source of truth.

Plugins inside the collaboration shell

The Control Center, Helix's multi-model collaboration shell, runs on an unmodified Mattermost server. I extend it only through its supported plugin model: everything Helix adds to its interface is a Mattermost webapp plugin in React and JSX, and the plugins are thin.

Rust control plane and PostgreSQL: conversations, history and state

Drawn to suggest weight, not measured. The plugins can be redeployed without touching any of what sits under them.

A work tab inside Teams

In Teams, the working service has a tab built with React and Microsoft's Fluent UI, so it looks native where it appears. A user signs in through Teams single sign-on and hands work to a coding agent on an approved machine or in the cloud.

sign-onsubmittracked from the tab while the agent worksdone

Approved machine

no inbound connections

Or the cloud

the same submission

Illustrative durations. Cancel is available from the tab at any point in the shaded span.

A meeting stage the agent can drive

The third surface came from a dead end. Microsoft's native presentation feature gives an agent nothing to hold, and I would not have the agent pretend to present. I built a Teams meeting-stage app, with stage, side-panel and configuration views, and a small authenticated Node relay with its own test suite. The meeting-action server uses it to start a deck on the shared stage, move through it and stop it. See A meeting attendee that will not fake it and Solving the digital-employee identity.

Where a vendor feature has no control an agent can use, I build a surface I control.

The exact tenant, employee and meetingmatch
The slide revision it expectsguarded
Anything elsefails closed

Two actions cannot fight over the stage.