The independent workspace for professional agent work.

Built for engineering teams that need control.

hob workspace interfacehob workspace interface

Works with the inference your team already uses

Claude Code
Codex
OpenCode

Always run the best model.

Your subscriptions stay separate from your workspace, so switching agent, provider, account, or model is one click. Your work no longer lives inside one provider’s ecosystem.

Type a message...

Built from scratch
for agent work.

Every tool you need to direct AI, in one workspace. Always at the frontier of agentic coding, so the work stays consistent and predictable, gets easier, and lets you do more.

iPhone
Type a message...
CodexGPT-5.5XHigh

Private by architecture.

Conversations live in a local database on your device. Remote access encrypts workspace traffic before it reaches the relay. The hob team cannot read your panes, agent sessions, files, or history.

hob encrypted remote workspace previewhob encrypted remote workspace preview

In practice

Use hob to execute complex agent work. The tools the job needs are already there.

Automations

  • Automate recurring work, like reviewing and addressing user feedback.
  • Define the steps once, so every run does exactly the same thing.
  • Secrets hold the keys your automations need. No agent gets them, so no provider does.
  • Auto-start anything that needs to stay on while the project is open.
hob's Automations panel: run counts, saved automations with their status, and stored secrets

Pull requests

  • Open pull requests, comment on them, and close them where the work happens.
  • The diff, the conversation, and the change in one place.
  • Run hob pr from an agent, or drive the PR surface by hand.

Remote issues

  • Create, comment on, and close issues on GitHub, Gitea, or Forgejo without leaving hob.
  • Hand any of them to an agent to fix.
  • Agent-made issues stay linked to the conversation that produced them.

Agent control surface

  • Every agent you run can operate hob itself, not just edit your files.
  • They open the files, diffs, and panes you need, so you stop hunting for them.
  • One agent hands work to another, and both keep running side by side.
  • Ask how something works and the agent walks you through the interface.
A hob workspace with the project sidebar, eight workspace tabs, and an agent pane open

Remote access

  • The full workspace in a browser, and a phone companion for steering agents on the move.
  • It drives your actual desktop session, not a copy of it.
  • Traffic runs through an encrypted relay. hob never opens a port to the public internet.
Line illustration: a laptop running hob and a phone, joined through a relay in between

Worktrees

  • Give agents separate worktrees when their tasks need isolation.
  • Your main tree stays clean, and parallel edits stay out of each other's way.
  • Keep the branch when the work lands. Throw the worktree away when it doesn't.
hob is the most useful thing I pay for right now. With how fast agentic coding changes, staying current used to be a pain. Now I can pick up whatever ships this week and my workflow stays organized and predictable.
Marc Llopart

Marc Llopart

Analytics Engineer/nansen.ai

I used to run 6+ Claude Code instances in my terminal, and coming back to them was a nightmare. Now I can shut my laptop and free up the RAM in my head. Every workspace is right where I left it, ready to resume.
Adrià Torralba-Agell

Adrià Torralba-Agell

Blockchain Security Researcher/openzeppelin.com

Questions & answers

hob runs locally and stores agent conversations in a local database on your device. Regular hob service traffic is limited to read-only checks like app updates and model-list updates. Agent work goes between you and whatever agent provider you already use, such as Anthropic or OpenAI. hob is the interface, not the middleman.

Pro+'s remote access uses our managed relay at roam.hob.dev. Frames are end-to-end encrypted by hob on top of WebSocket TLS before entering the relay, which forwards encrypted frames only. It does not have the plaintext needed to read your workspace or session data.

Your existing tools give you model access or editor-specific workflows. hob gives you the workspace layer that holds them together: parallel sessions, terminals, local history, remote access, and project context across whatever providers you already pay for.

No. hob is not a model provider and does not resell tokens. You bring the agent CLIs, model accounts, API keys, and routing choices you already use. hob gives those tools an independent workspace around them.

hob is for developers who already use agent CLIs as part of real engineering work, not casual prompting. If you run Claude Code, Codex, OpenCode, terminals, multiple repos, or parallel agent sessions daily, hob gives that work one durable, local-first workspace.

hob probably is not worth it if you only use AI coding tools occasionally or mostly chat with one model in one app. hob is built for developers whose agent workflows are frequent enough that organization, history, portability, and control matter.

Everything stays on your machine. Your local database of conversations, workspaces, and history is yours and remains accessible regardless of subscription status.

Give your agents
a professional workspace.