Vibetight
Concepts

Bring your own coding agent

What runtimes Vibetight supports today, what's on the roadmap, and how the abstraction layer works.

Updated 2026-05-19

Vibetight is the project-management layer for coding agents. The agent itself (the model, the tool-calling loop, the provider) is pluggable.

Today

We ship support for the leading coding-agent provider out of the box. You bring your own account (subscription or API key, declared per-device for billing-mode clarity) and Vibetight runs the agent process on your paired device when work lands on a task.

You’re never paying us for the agent’s compute. We coordinate. The agent runs against your contract.

Roadmap

  • OpenCode: actively in development. Same abstraction; same workflow.
  • More runtimes to follow. The internal runtime selector is built around a common interface; adding a runtime is a single class implementation, not a fork.

We’re not making promises about specific providers or specific dates until we have something demoable. What we will say: the architecture assumes a heterogeneous future. You’ll be able to run different agents on different devices, or even different agents per task, without changing how the board works.

Runtime-agnostic by design

The board, the dependencies, the permission flow, the diff review: none of them care which agent is behind the runtime. Adding a new agent doesn’t change how Vibetight works, just which engine does the typing. That’s the whole point of separating the project-management layer from the agent layer: pick the best agent for each piece of work, change your mind later, never rebuild your workflow.

Auth mode declaration

Each paired device declares its agent’s auth mode at pairing time:

  • Subscription (e.g. a Pro/Max account on the leading provider). The device is treated as personal: only the owner of the device can interact with agents on it.
  • API key / programmatic. The device can be shared across a workspace, agents on it can be assigned to anyone.

The distinction is there because some providers’ terms of service forbid using a personal subscription as a multi-user backend. We enforce that at the product layer so you can’t accidentally violate your provider’s terms.

What this means for you

  • Don’t lock yourself in by picking a provider. Vibetight is designed to outlive whichever single agent you’re using today.
  • Don’t pay us for tokens you’re already paying your provider for. We meter agents, projects, and tasks shipped, never your provider tokens.
  • Watch the roadmap (and Maestro MCP, which is already provider-agnostic by virtue of being open MCP) for what’s landing next.