jj let me make changes to my git commits without fear, since version control of the git state itself let me undo those changes easily, too.

[1]: https://github.com/grpc/grpc-go/blob/06fc26a196350499dd0cf2d...

Also “tasks.create” is morally a route. Eg grpc has web transports and autogenerated CLIs too; even without those, there’s no particular reason why the OBI “client layer” couldn’t just be, say, gRPC under the hood, with the OBI specs just being used to codegen adapters from the source protocol to gRPC. It would then immediately have a much more widely understood and supported client layer, with better performance, while remaining as simple to implement as the adapters to this new custom OBI runtime protocol.

OBI is a boilerplate generator for the adapter pattern for service communication; its contracts are just another set of their own paths, payload shapes, and protocols. The distinction between “protocol” and “contract” in this context is nonsense.

Even purely on the technical level, this seemingly hasn't internalized the lessons of https://xkcd.com/927/

For those familiar with idb, some of iosef’s agent-oriented features include:

Directory-level sessions, so agents in different worktrees don’t interfere with each other’s simulators.

Automatic scaling of screenshots into the same coordinate space as the accessibility trees and interaction tools.

Selector-based interactions, to save LLMs from needing to re-consult accessibility trees or screenshots each turn.

Skills and MCP support.

=====

iosef’s absence from the pre-training corpus means agents need a little nudge (either via the skill or user prompt) to use it over idb or simctl—but once they’re using it, they have a easier time than they do with other tools. While written in swift, it’s packaged via pypi for easy running and installation via uv (eg “uvx iosef --help” or “uv tool install iosef”).

Is it nearly entirely vibe-coded? Yes—but I’ve found it helpful for my own use, so I share it in case others will, as well. And this post is entirely human-written, so at least there’s that.

Comments URL: https://news.ycombinator.com/item?id=47203961

Points: 1

# Comments: 0

2. A “runtime scheduler for humans” that I wished existed, too (think morning routines, travel checklists, and pomodoros in the same abstraction—but also a lot of support for ad-hoc rearrangement and addition of the task queue).

jq says hello!