03 / AI developer tooling · Personal / open source
A workflow that goes
beyond the prompt.
I use coding agents to work through unfamiliar systems and deliver software. My private harness makes context, scope and verification explicit. My public contributions improve the provider integrations these workflows depend on.
Private development harnessOpenCode first · Codex compatible
TypeScript contributionsThree selected merged PRs
Engineering focusReliability, permissions & evidence
A look inside the approach
The task changes.
The discipline stays.
Illustrative workflows based on my harness design.
These controls do not run an AI model.
Start with the failure
Collect the symptom, relevant logs, deployed version and a reproducible path. Keep unrelated context out.
Test an explanation
Trace the affected code with read-only inspection first. Compare hypotheses with observed behavior before changing the implementation.
Verify the affected behavior
Reproduce the original failure, apply a bounded correction and check the reported scenario. Record what remains unverified.
A plausible explanation is a hypothesis until the evidence supports it.
The harness is a personal engineering project
I maintain shared instructions, reusable skills, task-based model routing, scoped tool permissions and context handoffs. OpenCode owns the primary workflow; compatible adapters keep shared behavior available in other coding environments.
Deterministic checks inspect configuration and contracts. Behavioral evaluations exercise tool use, specialist routing and continuity across compaction or a fresh-session handoff. A stored summary alone does not establish continuity; the agent has to retain the relevant information.
Selected contributions, accepted upstream
Cursor adapter · Merged September 2026
Bound worker capacity and isolate failures
Enforced bridge worker limits, reclaimed capacity before close callbacks, isolated callback failures and returned retryable HTTP 503 responses at saturation.
Read PR #33 and its validation ↗Anthropic plugin · Merged September 2026
Harden OAuth and the plugin lifecycle
Completed and hardened a V2 migration begun by another contributor, adding credential-refresh deduplication, request/response correlation, concurrency tests and package validation.
Read PR #211 and its validation ↗Cursor adapter · Merged July 2026
Route the model the account actually supports
Discovered available model and parameter combinations from the provider, then routed exact selected variants while preserving account restrictions.
Read PR #11 and its validation ↗What carries across domains
The same habits apply to a telecom API, a macOS authentication tool and an AI provider adapter: understand the boundary, make state explicit, handle failure deliberately and verify the result.
The harness repository stays private. The linked PRs are separate public contributions, not Nokia product work. The walkthrough illustrates the approach; it is not a recorded agent transcript or a performance benchmark.