caerule.
← Selected work

Open-source engineering

Four merged contributions spanning OpenCode, the Cursor adapter, reliable session compaction and Apple password rules.

I also maintain a private harness for task routing, scoped tool permissions and verification.

Public work
4 selected merged pull requests
Languages and data
TypeScript · JSON
Personal tooling
OpenCode-first harness · Codex-compatible adapters

Accepted upstream

Cursor adapter for OpenCode V2

Rebuilt the adapter around OpenCode’s messages and host tools, preserving exact model variants while making tool-driven runs recoverable without a second conversation store.

opencode-cursor · PR #35 ↗

Merged September 2026

Dialog keyboard event handling

Reproduced an Enter-key leak from OpenCode dialogs into the prompt, then corrected event handling across seven dialogs so confirmation no longer triggers the underlying input.

OpenCode · PR #23390 ↗

Merged April 2026

Reliable session compaction

Forked the source session for summarization so the model could see assistant turns; a live probe confirmed it recalled assistant-only facts correctly.

magic-compact · PR #10 ↗

Merged July 2026

Personal development harness

I maintain shared instructions, reusable skills, task-based model routing, scoped tool permissions and context handoffs. OpenCode is the primary host; compatible adapters make the shared behavior available in other coding environments.

Configuration checks validate contracts. Behavioral evaluations exercise tool use, specialist routing and whether relevant information survives compaction or a fresh-session handoff.

The harness repository is private. The linked contributions are separate public projects, independent of employer product work. I do not have a measured productivity benchmark for the harness.

Explore example development workflows

Task workflow examples

Illustrative workflows based on my harness design.
These controls do not run an AI model.

Example task
01 / Context

Start with the failure

Collect the symptom, relevant logs, deployed version and a reproducible path. Keep unrelated context out.

02 / Scoped work

Test an explanation

Trace the affected code with read-only inspection first. Compare hypotheses with observed behavior before changing the implementation.

03 / Evidence

Verify the affected behavior

Reproduce the original failure, apply a bounded correction and check the reported scenario. Record what remains unverified.

Output: a reproduced failure, a tested correction, and any remaining verification gaps.