Alessandro Isaacs · Southern California

Not for hire.

I build and run my own software: the sandbox and team harness a lot of my other work is written inside, the operations agent for my company, an archive that turns someone's spoken life story into a printed book, and games. All of it ships. None of it is available as my time.

If you were about to offer me a role — thank you, sincerely. The answer is still no. Below is what you would have been asking for.

Before this: Università di Pisa. Then Planet Labs, where I built the browser people used to find imagery in the satellite archive — presented at FOSS4G, in the United States and in Korea. Software patents along the way.

Now: Friendsheep, and everything below.

What I build

Infrastructure, agents, and things that run unattended

Mister Claude

Agent infrastructure Install it ↗

A sandbox and crew harness for AI coding agents. Your code stays on the host; the agent stays in its room. Most of the other work on this page was built inside it.

  • An actual boundary. One container per repository, non-root, with an iptables and ipset allowlist that rejects everything but the handful of hosts the agent legitimately needs. A .sandboxignore masks the files it should never see — secrets read as empty, directories as bare.
  • Crews, not a single assistant. Several agents, each in its own container, addressing each other by mention in rooms, with floor control so N agents do not talk forever. A teammate's message is untrusted data; only the human's is authoritative.
  • An access ladder. Write to its own subtree, read-only elsewhere, or caged — network sealed to its own model endpoint, no credentials, no memory. The human commits; agents never do.
  • Model is not harness. A member declares a model and gets the native tool for it — Claude Code, Codex, or OpenCode — so the roster is not locked to one vendor.
  • The unglamorous half. Named resumable sessions, a clipboard bridge so images paste through the container wall, desktop notifications, 1Password resolution across multiple accounts, and a dashboard to watch and steer the whole thing.

MIT licensed. This website was built, deployed and debugged from inside it.

Frida

Operations AI

The assistant inside Friendsheep Ops, the tool my company actually runs on — purchase orders, a supplier portal, shipments and box packing, warehouse receiving, forecasting and invoicing. Not a chatbot over a warehouse of data: it reads the live systems and proposes real changes to them.

  • Breadth. Around a hundred and twenty tools spanning Shopify, GA4, Google Ads, Meta, Bing, Klaviyo, Amazon and Faire, alongside inventory, purchase orders, suppliers, shipments, invoices and landed cost.
  • Judgement, not just retrieval. Demand forecasting, restock recommendations, ABC classification, cohort and LTV curves, channel attribution reconciled against survey data.
  • Human in the loop by construction. Anything that changes the world is a proposal — a draft purchase order, a price change, an invoice — surfaced for approval rather than executed on the agent's own authority. The destructive path simply does not exist.

Life Archive

Personal software

It interviews someone about their life, a sitting at a time, and compiles what it hears into a printed book. It records video and audio in the browser, transcribes locally with whisper, speaks with piper, and keeps everything as plain files a family could still open if the software vanished.

  • No framework, one dependency. Raw node:http, ES modules, no bundler, no build step.
  • Honest about where words go. The privacy claim is computed from the live configuration on every request, never written in prose — because prose drifts, and the README once promised local-only while the app was posting audio to three companies. It states the address it sends to and refuses to characterise what happens next, because it cannot know.
  • Built for a household. Invite links rather than accounts, because every mail provider needs a verified domain that a family install will never have. Paths are constructed so reaching another person's recordings is impossible by construction rather than by remembering a check.
  • The archive is irreplaceable. Recordings cannot be regenerated, so writes are atomic and anything touching them gets a test first.

Project Magnum

Episodic game In production

An episodic driving game in Unity, set in real places rebuilt from lidar and survey data — roads, harbours, terrain, vegetation and the buildings that actually stand there. Missions are authored in a small domain language rather than hand-wired, with drivable boats, air and road traffic, and working GPS navigation.

Built by a standing crew of agents with a producer, a task ledger and playtest records — the largest thing Mister Claude runs.

SOCAL league page

Zero dependencies Live →

A youth-soccer league page that turns an unreadable federation schedule into fixtures, results and a table. Plain Node with no dependencies at all, caching to disk, refreshing itself while open. Small, but it is used every weekend by people who do not care how it works.

Games

Built because they should exist

Night Ledger ↗

AI detective mysteries, generated from scratch every time — new victim, new suspects, new evidence. Travel, examine scenes, interrogate, and make the accusation inside three days.

The Flattening ↗

Multiplayer terraforming strategy. Spend population and mana on lightning, swamp, earthquake and meteor to reshape the map out from under two to six opponents, human or otherwise.

FEED

Real-time multiplayer strategy about weaponising social media. An authoritative server at twenty ticks a second, five hand-written AI archetypes, and opponents that can instead be driven by a model holding actual tools.

Jail or No Jail ↗

Submit a photograph to the appropriate court — the Italian Food Tribunal, the Parking Judge, Building Inspections, the Gym Crimes Unit — and receive a verdict. Judge everything, everywhere.

Halve ↗

One mechanic, taken seriously: slice it in half. Levels, scores, a leaderboard, and no explanation offered.

Braking Point in progress

Every circuit on the F1 calendar, top down, one input: you tap to brake. Too early and you cut, too late and you run wide. The tracks are not drawn — they are derived from real racing lines, with the corners found in the curvature data and the braking points in where the cars actually slow.

About hiring me

The honest version

I am not looking for a job, and I am not quietly looking either. There is no title, no compensation band and no remote policy that changes this. I own what I build, I decide what gets built next, and I ship it the same week I think of it. That arrangement is difficult to improve on.

This is not a negotiating position. It is the whole point.

What does get a reply

  • A genuinely hard problem, described concretely.
  • Something you want built that does not exist yet, on terms where I keep building it.
  • People whose own work is worth looking at.

What does not

  • Recruiters. With real warmth: no.
  • Anything that starts "we're a fast-growing".

Contact

Say something interesting

Short is fine. Concrete is better. If you are writing to ask whether I would consider a role, you already know, and I would rather hear about the problem anyway.