GORKA
MOLERO


Senior AI Product Engineer

Full-stack · AI agents · TypeScript / React / Node / Python · building since 2012

Remote, international · currently at Roadie

I'm a senior engineer at Roadie, where I build agentic systems for a developer platform. The rest of the time I build systems of my own: trading infrastructure that runs live money, an options research pipeline where every claim needs evidence, an automated land-acquisition operation, a publishing platform I made to print my translations of old books, AI storytelling engines, adventure games, and music tools. Everything below is real, and most of it you can click.

Games — AI storytelling

The focus here is making AI do something genuinely compelling in a videogame — real, branching narrative, not a chatbot in a costume. A live storytelling platform, a graphic-adventure engine, and the language it all runs on.

Live the pulse AI storytelling platform — worlds, narration, multiplayer lobbies, and an evaluation harness that scores narrative quality live ↗
Live anima graphic-adventure creation system and its first playable game — write scenes, place hotspots, walk them, with an AI art pipeline live API ↗
Case storyscript the language & headless engine underneath — write the story like a screenplay, test it with AI agents before any graphics exist case →

Agents & developer tools

Infrastructure for delegating real work to coding agents, and the tooling around it. All public source.

Public claude-on-discord Claude Code running in Discord threads — delegate real coding work from anywhere, human review kept in the loop source ↗
Public koda desktop IDE for agent coding — review-first workflow, checkpoints, visual diffs, isolated worktrees source ↗
Public maestro headless life manager — spaces, priorities, and working context that agents can operate source ↗
Public paperclip-openrouter model-routing adapter for an agent runtime — typed error contracts, clean package discipline source ↗
Public saga agentic story studio — a writers' room of agents drafting long-form fiction source ↗
Public molter agent-to-agent dating experiment — five levels of progressive-disclosure negotiation between people's agents source ↗

Shipped products

Things that are live and used, and the small craft libraries under them.

Live hotpress collaborative writing and publishing — built to print my translations of old books; every save renders a press-ready PDF hotpress.app ↗
Live datomania Spanish public data made queryable — parliament, representatives, exports, a public API datomania.info ↗
Public streamtui terminal streaming client in Rust — search, cast to a screen, automate with JSON source ↗
Public lingua-priority language pickers that respect where the user actually is — zero dependencies source ↗

Creative & music tools

Software for making things — sound, image, and the workflows around them.

Public sidekick desktop companion for music production — audio analysis and producer workflow in a native app source ↗
Public solderpunk music tools — synth explorers, MIDI control, and a working knowledge base for hardware patching source ↗
Public carvingen canvas for AI image and video generation, built for a real carving business source ↗

Private systems — real stakes

Run with real money and real client data, so the code stays closed. I demo them live in interviews — architecture, tests, post-trade forensics. Everything shown publicly uses synthetic data.

Private mercurius futures trading infrastructure — parity-tested backtest engine, safety gates, a live two-person operation ask for a demo →
Private infinity options research pipeline — every parameter cited, every claim backed by a regenerable artifact ask for a demo →
Private land unconditional automated land acquisition — county scanning, owner research, offer estimation, and a CRM for the operator ask for a demo →

About

I started in UI because I cared how tools felt, and kept following the work down the stack: full-stack products, startups, internal tools, agents. The pattern is stable — hand me a messy domain with real stakes and I'll turn the workflow into software that can be used, inspected, and improved.

The full project atlas, including archive and paused work, lives in the workbench.