Vif

Stop letting issues die in the backlog.
Ship reviewed pull requests instead.

Give Vif a GitHub issue. It runs the work in a scoped sandbox, opens the PR, and brings back the context reviewers need before the queue keeps growing.

See the workflow
See pricing

Add OAuth device flow support #482

vif workflow run

Issue opened2m
Run started3m
Work in sandbox14m
PR created2m
Under review5m
Ready to merge

Run timeline

  1. run started
  2. analyzing codebase
  3. implementing changes
  4. running tests
  5. creating pull request
  6. awaiting review
feat(auth): add OAuth device flow support +129 -18
auth/device_flow.go auth/handler.go 
42 func StartDeviceFlow(ctx context.Context, client *oauth2.Config) (*DeviceFlow, error) {
43-   // old implementation
44+   // device flow implementation
45+   df, err := client.DeviceAuth(ctx, scopes...)
46+   if err != nil {
47+       return nil, err
48+   }
49     return df, nil
}

How it works

A clear path from issue request to reviewed PR.

Vif keeps the workflow inside GitHub, but makes each handoff explicit: what starts the run, where code executes, what lands in the pull request, and when your team takes back control.

01

Start from the issue your team already wrote

Use the normal backlog item as the source of truth instead of opening a separate agent task.

Trigger
Add the vif label or comment /vif implement.
Input
Issue title, description, repository, branch, and linked context.
02

Vif runs the work where it belongs

The implementation happens in the workspace selected for your access, capacity, and isolation needs.

Runtime
Managed hosted capacity, dedicated workspace, or custom deployment.
Control
Repository, MCP access, limits, and credentials stay scoped to the workflow.
03

The work lands as a normal pull request

Reviewers get the artifact they already know how to inspect: branch, commits, tests, and summary.

Output
Pull request with implementation notes and run status.
Review loop
Blocking feedback can be fixed before the handoff is marked ready.
04

Your team keeps the final decision

Vif prepares the PR. Your engineers still decide what is acceptable, what changes, and what merges.

Team action
Review, request changes, approve, or close like any other PR.
Audit trail
Issue, run, sandbox, review findings, and PR state stay visible.
Nothing leaves the review process. Vif moves work forward when the issue is clear; humans still own approval, merge, and production responsibility. Open workflow console

Vif turns GitHub issues into pull requests your team can review.

Vif is for engineering teams with more requested work than reviewer time. It takes a real GitHub issue, runs the implementation in a scoped workspace, and returns a pull request your team can inspect, request changes on, and merge.

Turn issues into pull requests

Use Vif when the problem is already described in GitHub and the next useful artifact is a reviewed PR.

Keep access clear

Start with Vif Cloud for standard GitHub work, or size a dedicated setup when private systems and team-specific tool rules matter.

Buy capacity, not guesswork

The simulator estimates how many coding workflows can move at once, then flags when the setup should be quoted instead of self-served.

Short answer

What is Vif?

Vif takes a GitHub issue, runs your connected coding agent in an isolated workspace, and returns the work as a pull request.

For teams

How is Vif different from an IDE assistant?

Vif is not a coding editor. It manages issue intake, workspace isolation, the run, PR creation, review status, and follow-up work around GitHub.

BYOA

Whose agent usage pays for the work?

Your connected agent account runs the work. Vif pricing covers orchestration, workspace capacity, queueing, and review handoff rather than reselling tokens.

Security fit

When is hosted Vif not enough?

Use a quoted runtime when work needs private systems, internal tools, custom MCP servers, team-specific access rules, compliance review, or unusual resources.

FAQ

Straight answers before Vif touches a repo.

The short version: Vif does not replace your review process. It gives implementation work a scoped place to run, then brings the result back as a pull request your team already knows how to judge.

Whose agent account does Vif use?

Vif uses the coding agent account your team connects. Bring your own agent means the work runs through your account, not a generic Vif-owned account.

What happens after we ask Vif to implement an issue?

Vif reads the issue, starts a scoped run, prepares the workspace, tracks the work, and returns the result as a normal pull request with notes and status.

Who reviews and merges the pull request?

Your team does. Vif prepares the PR and can handle follow-up work, but approval, requested changes, merge timing, and production responsibility stay with your engineers.

Which coding agents does Vif support?

Vif is agent-agnostic by design and BYOA-first in operation. Hosted Vif supports OpenAI Codex through your connected account today; dedicated or custom setups can scope additional agent profiles as they become available for your team.

Can we choose the model and effort level?

Yes. A workflow can choose the connected agent account, model, and effort level for each step, then combine that with approval rules, workspace boundaries, and allowed systems.

Does every workflow step share the same container?

No. Workflow steps such as implementation, review, and fixes run inside isolated containers with the workspace boundary assigned to that step.

How is Vif priced?

Managed hosted pricing is based on concurrent capacity slots, not token resale. Dedicated runtime and custom deployment setups are quoted from the access boundary, support, and resource requirements.

What is a capacity slot?

A slot is one issue-to-PR workflow running at the same time. Slot size controls the runtime resources available to that workflow, and extra compatible work queues until capacity is free.

When do we need a dedicated runtime?

Choose a dedicated or custom setup when the work needs private systems, internal documentation, custom tool connectors, stricter access rules, procurement, or security review.

Does Vif replace our developers or reviewers?

No. Vif moves implementation work into a pull request. Your engineers still review, request changes, approve, merge, and own production responsibility.

Start small. Add capacity when the queue proves it.

Shared hosted pricing is for standard GitHub work and published capacity slots. Private systems, custom tool access, and security review move the request into a quoted dedicated or custom setup.

Self-serve start

Clear shared pricing

Use managed hosted slots when the workflow only needs GitHub, your connected agent account, and the default hosted rules.

No token resale

Your agent account stays yours

Vif bills for orchestration and workspace capacity. Model usage remains with the account your team connects.

Quoted setup

Talk to us when access changes

Private networks, internal tools, custom MCP servers, compliance, or unusual resources are scoped before pricing is finalized.

Question 1 of 4

Where can the work run?

Start with the boundary your team is comfortable with. Hosted is fastest when it fits; private systems need a quoted setup.

Runtime Access Fit Capacity
Where can this work run?

Governance ready

SSO, audit logs, role-based access, and approval flows can be part of a custom deployment.

Access stays scoped

Tools, secrets, and sandboxes stay inside the workspace boundary recommended for your team.

Self-host or Vif Cloud

Run in your own cloud or use Vif Cloud. Your code, your choice.

Pricing wizard

Review your recommended setup.

Confirm the constraints, capacity, and contact details. The request will include the setup your answers point to.

Needs Capacity Review

Tell us how your team works.

No infrastructure vocabulary required. Pick the constraints you recognize and we will map them to the right setup.

Where can this work run?
Which requirements apply to your workflows?
Recommended setup

Managed shared runtime

Best fit when your team only needs standard GitHub issue-to-PR work and the hosted boundary is acceptable.
Talk to Vif

Send your question.

Send a direct question to the Vif team. We include your context in Slack so the right person can reply.