Services

Hands-on agent engineering for teams with real systems.

I build and fix the practical side of AI automation: the tools, integrations, and guardrails that let agents do useful work inside your stack. Engagements start with a conversation and are scoped to what you need.

Engagements

01

Agent & workflow integration

Connect agents to your repositories, APIs, and internal tools, with defined scope, approval points, and a clear record of what they did.

  • MCP / CLI tool connections
  • Multi-agent handoffs and review loops
  • Scheduled or event-driven runs
02

Custom developer tools

Purpose-built CLIs, plugins, and services that remove a repetitive step from how your team builds, reviews, or ships.

  • Coding-agent plugins and skills
  • Internal CLIs and automations
  • Repository and CI integrations
03

Prototype to working system

Take a promising demo, notebook, or script and turn it into something that installs, runs unattended, and can be maintained.

  • Packaging and deployment
  • Configuration, storage, and APIs
  • Docs your team can actually follow
04

Troubleshooting existing automation

Diagnose agents or pipelines that loop, stall, overreach, or fail quietly, then tighten the boundaries and checks around them.

  • Runaway or stuck agent runs
  • Unverified handoffs
  • Brittle integrations

Capabilities

Demonstrated in shipped projects.

These are applied engineering skills, shown in public work like Dead Drop. This is not model-training research, and there are no promises that an agent will never need a human.

Repository & API integration
Agents that work in real codebases and services, not sandboxes.
Persistent coordination
State that survives restarts, machines, and providers.
Human approval boundaries
Explicit points where a person decides before anything irreversible happens.
Validation
Checks against exact commits, test runs, and evidence rather than self-reports.
Connecting to real systems
From Linux services to radios and cloud pipelines.

Supporting work

The layers under the agents.

Automation is only as good as what it connects to, so the work covers the software, hardware, and hosts too.

Software

  • Python, FastAPI
  • TypeScript, Node.js
  • WebSockets, REST, MQTT
  • SQLite, browser UIs

IoT & radio

  • LoRa / Meshtastic / MeshCore
  • Raspberry Pi & SX1302 hardware
  • Edge-to-cloud telemetry
  • Home Assistant integration

Linux & networking

  • systemd services
  • Hardware autodetection
  • Install & update tooling
  • Network-facing dashboards

How engagements work

By inquiry, scoped together.

There are no packages or fixed price list. Each engagement is scoped to the problem.

  1. Step 1

    Inquiry

    Message on X with the system, the goal, and the constraints.

  2. Step 2

    Scope

    We agree on what gets built, what stays manual, and how we will know it works.

  3. Step 3

    Build

    Work happens in your repositories, in small reviewable pieces.

  4. Step 4

    Hand off

    You get working code, the docs, and an honest list of known limits.

Start a conversation

Have a workflow that should run itself?

Send a short note about the system, what it should do, and where people need to stay in the loop.