---
title: "Portfolio"
description: "This is a working record of the systems I have built, contributed to, and shipped: open-source agent infrastructure, protocol-facing product engineering, and personal tooling built around orchestration, memory, and legibility."
canonical: "https://www.symbaiex.com/portfolio"
last-updated: "2026-06-24T12:00:00.000Z"
---
# Portfolio

This is a working record of the systems I have built, contributed to, and shipped: open-source agent infrastructure, protocol-facing product engineering, and personal tooling built around orchestration, memory, and legibility.

## Projects
### [ElizaOS](https://www.symbaiex.com/portfolio/elizaos)

**Open-source AI agent ecosystem** — Open-source agentic operating system contribution work around practical extensibility, integrations, and production-minded AI agent patterns.
Role: Contributor / integrator / reliability-focused systems engineer. Timeframe: 13 public PRs.
Tags: ai agents, open-source, integrations, systems

### [Babylon](https://www.symbaiex.com/portfolio/babylon)

**Social protocol product engineering** — High-volume contribution work on BabylonSocial, connecting product velocity with maintainable implementation details.
Role: Engineering contributor. Timeframe: 159 public PRs.
Tags: social, product, engineering

### [Hyperia](https://www.symbaiex.com/portfolio/playhyperia)

**Interactive product and AI tooling** — AI-native MMORPG work through PlayHyperia/HyperForge, where agent behavior and player-facing systems meet.
Role: Product systems contributor. Timeframe: 42 public PRs.
Tags: ai, interaction, product

### [OpenController](https://www.symbaiex.com/portfolio/opencontroller)

**Personal open-source software** — Open controller patterns for interoperable orchestration, control surfaces, and operator-friendly workflows.
Role: Creator / systems engineer. Timeframe: Personal project.
Tags: controllers, orchestration, open-source

### [UsageMax](https://www.symbaiex.com/portfolio/usagemax)

**AI usage observability platform** — A private-by-default usage ledger that brings supported AI coding histories into one view of tokens, models, tracked cost, sessions, and activity.
Role: Creator / product engineer. Timeframe: Public app and npm CLI.
Tags: ai, privacy, observability, typescript

### [SYMindX](https://www.symbaiex.com/portfolio/symindx)

**Agent runtime and character systems** — A modular, agent-based AI runtime for emotionally reactive characters across games, web surfaces, and social platforms.
Role: Creator / framework engineer. Timeframe: Personal project.
Tags: ai agents, runtime, games, typescript

### [SymClick](https://www.symbaiex.com/portfolio/symclick)

**Native macOS utility** — A native menu-bar autoclicker with a global start/stop shortcut, configurable click patterns, and optional count or duration limits.
Role: Creator / maintainer. Timeframe: v1.2.0 public release.
Tags: macos, native, automation, utilities

### [doolittle](https://www.symbaiex.com/portfolio/doolittle)

**Agent migration and runtime tooling** — TypeScript workspace for ElizaOS migration and agent runtime experimentation.
Role: Creator / migration engineer. Timeframe: 2026.
Tags: typescript, elizaos, agents, migration

### [SYMLog](https://www.symbaiex.com/portfolio/symlog)

**Logging and monitoring system** — A modern logging and monitoring system shaped around operational visibility and developer feedback loops.
Role: Creator / tooling engineer. Timeframe: Personal project.
Tags: observability, monitoring, typescript

## What is in here

Each entry below is a real project, not a case study written after the fact. Some are high-volume contribution work on protocols and products other people run in production. Others are personal projects I started to solve a problem I kept running into, or to test an idea about how agents, control surfaces, and observability should behave. A few are formal, proof-level work where correctness is the whole point.

## How to read a project card

Every project follows the same shape: what it is, the problem it responds to, the approach I took, and the outcome. That structure is intentional. I care less about listing technologies and more about showing the reasoning, so you can judge the work the way I judge it myself: does it hold up under real use, and does it stay legible once the first version is no longer new.

## Where to go from here

If you want the origin story behind this body of work, the About page covers how I got here. If you want to go straight to the source, most entries link out to the live homepage, the repository, or both, so you can see the code and the running system for yourself.