For teams · Use cases

Small tasks, right at the relevant excerpt.

AYVI works where a developer is already working: with selected code or text. Fit depends on the app and its access to selected text.

Demo documentsrc/payment-flow.swift

18guard let account = session.account else {

19return nil

AYVIExplain code

Stops when there is no session with an account.

Example result− return nil+ throw AuthError.missingAccount
WorkflowSchematic view: selection → explanation → diff. The result and interface are examples.

Three scenarios

From understanding to revision

  1. Get oriented in unfamiliar code

    Select a method or condition and ask about its purpose, flow or dependencies. It can support more focused onboarding questions; time savings have not been measured.

  2. Review a proposed change

    Ask for a targeted diagnosis or improvement. Inspect the before/after diff and choose whether to accept it.

  3. Revise recurring text

    Polish, summarise or translate selected text in the HUD. The target app must expose editable selected text.

Requirements

Integration depends on each app

On macOS, AYVI needs Accessibility permission. Some apps expose selected text only partially; there is no systematic compatibility check for every app.

Open app-specific notes