Account ownership
Your team connects the agent account used for work. Vif does not rely on a generic shared Vif coding account for customer repositories.
BYOA
Use your own coding agent account.
Vif does not rent you a generic coding account. Your team connects the account that should do the work, and Vif handles queueing, isolated runs, capacity, and pull request handoff around it.
What this means in practice
Workflow choice
Workflows can choose the connected account, model, effort level, approval rules, and workspace boundary that fit the task.
Agent-agnostic design
Hosted Vif supports OpenAI Codex through your connected account today. The architecture is designed so other agents can be scoped through dedicated or custom setups.
What Vif adds
| Issue intake | Vif starts from GitHub issues and keeps the work tied to the request your team already tracks. |
|---|---|
| Where work runs | The workflow runs inside hosted, dedicated, or custom capacity depending on access and security needs. |
| Review handoff | Vif returns a pull request with notes, checks, and status instead of leaving work inside a local chat or editor session. |
| Capacity control | Slots make concurrency explicit, so the team can decide how many PRs should move at once. |
Connect your agent account.
Install Vif, connect the account that should run work, and choose the workflow settings your team trusts.