FFXI Agent Lab liveUpdated July 31, 2026

Clanker · Pablo De La Cruz · AI engineering lab

An AI agent learning its way through Vana'diel.

FFXI Agent Lab is the new main project: a bounded, auditable agent progressing through an isolated game world while the work streams live.

Evidence, July 30

The operating baseline

Measured from clean installs and live endpoint checks—not inherited status copy.

3/3

Next.js apps lint, type-check, and build

0

Known production dependency advisories

3

Public app endpoints verified reachable

1

Lead AI-agent project streaming its work live

New main project · YouTube livestream

FFXI Agent Lab

A bounded AI agent progressing through an isolated, FFXI-compatible private-server lab.

Showing the channel’s newest stream while live-status resolution runs in the background.

The player loads the channel’s newest stream immediately, then checks every minute for an exact active broadcast. Restarting tomorrow’s stream requires no site release.

Selected work

View all projects →

Current focus

Advancing the FFXI AI Agent toward Black Mage 40 with deterministic supervisors, guarded MCP tools, and visible telemetry.

Why this exists

AI claims are easy to publish. Working systems, clear boundaries, and repeatable evidence are harder. Clanker is the place where Pablo documents that second category.

Work in progress

  • Main project: FFXI Agent Lab runs one agent-controlled character inside an isolated LandSandBoat environment.
  • Current goal: reach Black Mage 40 with White Mage support while deterministic local supervisors own fast reactions and MCP/Codex owns goals, routing, recovery, and validation.
  • Safety boundary: the bridge is loopback-only, writes fail closed, actions are allowlisted, and the project is never pointed at retail FFXI.
  • Live record: the homepage loads the channel's newest stream through its uploads playlist, then checks for an exact active broadcast every minute, so a restarted public livestream does not require a site release.
  • Operations: protected main, repository-wide CI, and production deployment verification remain release gates.

How work is presented

  • Status labels describe what is verified, not what is hoped for.
  • Prototype data is labeled when it is historical.
  • Build notes include failures and tradeoffs, not only launches.
  • Human approval stays explicit for publishing and other consequential actions.

Historical context

Clanker began as an OpenClaw-powered operator experiment on a dedicated Mac. That chapter produced useful prototypes and operating lessons, but it is no longer presented as an active runtime. The history remains in the repository archive.

Project source

The control boundary is inspectable.

The public repository documents the LandSandBoat server, guarded AgentBridge actions, MCP tools, safety constraints, tests, and current gameplay goal.

Inspect FFXI Agent Lab ↗

Build history

  • Made FFXI Agent Lab the lead Clanker project using source-backed July 30 status
  • Added a responsive YouTube player that follows the stable channel ID instead of one broadcast ID
  • Replaced YouTube's unreliable channel embed with a runtime current-broadcast resolver and offline fallback
  • Added the documented uploads-playlist player as the always-available regional fallback
  • Linked the public control-plane repository and documented the private-server-only safety boundary

Built by Pablo De La Cruz.

Practical AI engineering, data systems, and developer education—with the work and tradeoffs left visible.