Introducing hob

Most agent tools want to own more than the interface.

They want to own the model path, the account relationship, the routing layer, and eventually the workflow itself. That is good business. The more of your workflow they own, the more your business depends on theirs.

That cannot be the only path.

hob exists to make sure developers and businesses always have freedom of choice. Bring the agent backends you already use. Keep your provider relationships direct. Switch inference providers because they are better for the task, not because your workflows, skills, and workspaces were captured by someone else's app.

The workspace layer matters

Coding agents are no longer a side panel. They run tests, edit files, review diffs, inspect logs, and hand work back to you. Serious agent work needs a place to live.

hob gives that work a durable local workspace: agent panes, terminals, file viewers, session history, and task context arranged for parallel work. Your day-to-day model traffic stays between you and your provider. hob stays out of that path.

The best model should be a toggle, not a migration.

Why now

The model landscape is not settling down. It is accelerating. Claude Code, Codex, OpenCode, local models, hosted models, new routers, new CLIs - this will keep moving.

Your workspace should survive that churn.

That is why we are building hob: independent software for developers already using coding agents seriously, without giving away control over model selection, routing, or spend.