Homunculus

a Journey

Filed: Year 2026

From OpenClaw to Homunculus

"Seven days with OpenClaw. On the eighth, I forged a new engine."

Frontispiece

Task→Outcome

The Shift

The transition from a tool (Solve this task) to a partner (Create this outcome).

Observation: In 2026, the engine ceases to be a hand-cranked apparatus and becomes a self-aware agent.

Fig. I: The Paradigm Shift
Outcome Theory Diagram
Plate I

Feels Wrong!

The Tool

Precise input. Predictable output.

The Problem Solver

Given the destination, it arrives at an outcome.

Plate II

Agenda

a Journey of Discovery

The Shift → The Marvels → The Failures → The Rebuild → The Future

Plate IV

The Workspace as Mind

Principle: Visible cognition

The workspace exposes the machine's instructions, memory, and daily trace.

Result

Inspectable. Versioned. Durable.

The engine remembers in plain sight.

Fig. V: The Workspace Mind
Workspace Mind Diagram
Plate V

Autonomy in Practice

Old Apparatus: Hand-cranked

You steer every valve by hand.

New Engine: Self-routing

State the outcome. The machine arrives at that outcome through trying, observing and trying again.

Plate VI

Memory That Persists

Chamber I: Daily logbooks

Automatic snapshots. Context preserved before compaction.

Chamber II: Curated ledger

Long-term knowledge loaded into each main session.

Plate VII

Skills — Drop-In Brasswork

Cartridge: Metadata

Name, description, and gates define the fitting.

Doctrine: Instruction Sheet

Capability arrives as text, not code changes.

Effect: New Bling

Write doctrine. Slot it in. The engine gains a new trick.

Plate VIII

When the Boiler Bursts

Days 1–7

"This is the future."

"It actually reasons."

"The openclaw is brilliant."

I was sold.

Critical Fault

When a collaborator fails, it hurts more.

This is not a tool crash.

It is trust venting into steam.

Plate XI

Config Failures

Documented Fault

Failure Modes

  • Unknown Key: Config rejected
  • Bad Type: Validation fails
  • Bad Value: System stalls
  • Trailing comma → refuses to start
  • Config change → wipe on snapshot load

The Spiral

[Loop Detected]
OpenClaw: *reloads*
OpenClaw: *restarts*
[Status: Stall]

One bad edit → restart loop → context lost.

Fragile config destabilises the entire engine.

Plate XII

The Wrong Trust Model

Security Fault

Local Trust Tangle

Agent, browser, files, and credentials sit in one blast radius.

Insecure deployments, exposed gateways, attack traffic in the wild

Fig. XV: Trust Boundary Failure
Wrong Trust Model

Too much power in one boiler.

Plate XV

Realisation

I already have a Hammer

Keep

  • Workspace as mind
  • Memory
  • Skills
  • Pluggable LLMs

Replace

  • Stability
  • Security model
  • Deployment

Keep the paradigm. Rebuild the chassis.

Plate XVIII

Enter Homunculus

Design Brief

Specification

  • Self healing
  • Secure by design
  • Hosted
  • MCP-first
  • Elixir/OTP-powered

Ingredients: Elixir, Phoenix, Firecracker, PostgreSQL

Homunculus Emblem
Plate XIX

Architecture

Frontend UI

Isolated environment. No direct access to secrets or workspaces.

Secret Store

Per-user encrypted vault. Agent never sees credentials.

User Container

Per-user workspace container. No cross-container communication.

Secrets never enter here. All external access via MCP only.

Isolation by Design
Plate XX

Fault Isolation

Supervision Trees

OTP supervision restarts only the broken part, leaving everything else running.

User Container

The agent inside is Elixir. It handles all workspace interactions.

  • Container crash → restart container
  • Agent crash → restart agent
  • Process crash → restart process

Frontend

Same principle: restart only the smallest affected part.

No full-page reloads. No full system restarts.

Granular fault recovery. The rest keeps running.

Plate XXI

Secret Handling

Per-User Encrypted Secret Store

User explicitly unlocks. User explicitly locks.

Locked = no long-running process can use a secret.

Go to sleep. Nothing breaks.

Future

Push notification to phone → unlock for task or time span.

Your secrets. Your control. Even when you're away.

Plate XXIV

Blast Radius

OpenClaw

Everything is local. Agent has full access to host, browser, passwords — everything exposed to the agent.

One breach, full exposure.

Homunculus

We use the browser as our battle-tested security boundary.

Agent runs in a hosted VM. We handle updates, firewalling, secure storage, secret management.

Throw desired outcomes over the fence. We do the rest.

Plate XXV

Why Elixir

Built for the Problems We Have

  • Designed around concurrency
  • Fault tolerance by default
  • Process isolation everywhere
  • Side-effect free processes communicating via messages

It's the 90s All Over Again

Erlang was built for telephone switches — millions of concurrent connections, zero downtime.

Today we plug users and agents into LLMs. Same problems. Elixir is the answer.

Plate XXVI

Learnings

The Problem

Solving engineering problems with non-deterministic engines (agents) is as hard as herding cats (developers) — just faster.

Elixir for Agent Architectures

Amazing fit. Processes, supervision, fault tolerance — it just works.

LLM-Backed Coding

Elixir works extremely well with AI coding environments.

LiveView Frontends

Fast, highly dynamic frontends without the JavaScript complexity.

Plate XXVIII

Throwing problems over the Fence

Plate XXV

Questions?

"Mind the steam."

ME → https://lnz.me

QR Code Finis

Want to Try?

Closed Beta
QR Code

getahead.now

Scan to join

Homunculus Emblem
Plate XIX