# How I am building Glassear Studio

_AI & XR_

My work as the founder and engineer of Glassear: designing the architecture and developing the AI tools that turn natural-language instructions into interactive XR experiences.

**Outcome:** An AI-native platform for building and modifying interactive XR applications across a web authoring environment and Unity runtime.

**Official product page:** [Glassear Studio](https://glassear.com/studio/)

## Problem

Creating interactive XR applications normally requires specialized tooling and manual coordination between authoring systems and runtime state.

## What I built

My work as the founder and engineer of Glassear: designing the architecture and developing the AI tools that turn natural-language instructions into interactive XR experiences.

- Natural-language-to-application workflows
- AI Planner and Intent Graph
- Agent and MCP tool architecture
- Structured scene/runtime modifications
- Hybrid deterministic and LLM architecture

## Architecture

An AI Planner and Intent Graph coordinate tool-based operations, MCP integrations, structured scene patches and runtime synchronization between a TypeScript/React/Node.js web platform and Unity.

## AI / agentic component

LLMs interpret intent and plan tool calls within explicit system constraints.

## Deterministic components

Typed operations, validation, reconciliation and runtime acknowledgements control how planned changes become scene state.

> Reasoning proposes changes; deterministic contracts validate, apply and synchronize them.

## Stack

TypeScript, React, Node.js, Unity, Python, PostgreSQL, MCP, LLM APIs, XR

## My role

Founder, architect and hands-on engineer

[View all selected projects](https://brunomoya.com/en/projects/)

---

Page: https://brunomoya.com/en/projects/glassear-studio/
This page in Spanish: https://brunomoya.com/projects/glassear-studio/
Agent index: https://brunomoya.com/llms.txt
Full profile as JSON: https://brunomoya.com/profile.json
Contact: bruno@glassear.com
