Omniweft · Engineering note
Omniweft adds authenticated local Python control
The merged PR-005 SDK adds private local sessions, capability negotiation, typed object transactions and explicit recovery after uncertain responses. Optional Vulkan presentation is also implemented, with separate Windows GPU evidence.
Source: https://louijiecompo.com/updates/omniweft-local-control/
GitHub records the Vulkan implementation and authenticated local Python SDK as merged on 13 September 2026. The SDK guide and examples at 3ab7bf114aa4acdef52387b1709be3fcaccb17b9 describe the implemented behavior; their remaining candidate language is stale against the merge record.
The host owns one volatile World and one active session. Renewed credentials retire earlier clients. Mutation responses that become uncertain require observation and explicit resynchronization, with no automatic replay.
The Python example is headless. Renderer verification covers a separate committed-snapshot fixture, with Windows physical-GPU evidence and Linux hardware presentation still not_run. This is a review of public evidence, not a new integrated agent-to-frame run.
Physics, persistence, richer mesh, voxel and pixel editing, multi-principal policies and performance targets remain future slices.
Follow the evidence
Read source evidence ↗ (opens in a new tab)
Related reading
- Retrying AI Workers Without Duplicating Actions
- From Python Agent to Vulkan Frame: Designing a Bounded Control Path
Follow writing and engineering notes
Add this feed to your RSS reader to follow new articles and engineering notes. No signup or tracking on this site.
Follow via RSS