Skip to content
Appvecta

Six named features

Six features, one loop.

Each of these is being built as part of a single cycle: understand the project, plan a change, make it, run it, drive the real flow, collect evidence, and repair. None of them is a standalone add-on.

Appvecta Brain

A persistent graph of your project, built by reading the code and never by running the build. It is what lets everything else in Appvecta answer questions about your architecture.

A working memory for your codebase.

Appvecta Impact

Ask what a change affects and get the blast radius grouped by layer — model, persistence, UI and state, background work, and the tests likely to break.

Know the blast radius before you type.

Appvecta Agent

Bring your own provider — an installed Claude Code or Codex CLI, an API key, or a local Ollama model. Every multi-file change is planned, approved, applied and revertible.

Bring your own model. Keep the approval.

Appvecta QA

Describe a flow, review a deterministic plan built from selectors that actually exist in your source, approve it, and run it on hardware — with evidence captured at every step.

Run the real flow. Keep the evidence.

Appvecta Device Hub

Build, install, launch and drive Android and Flutter apps without leaving the editor — with run targets discovered by parsing your project, not by running Gradle.

One toolbar instead of five windows.

Appvecta Replay

Reproduce a bug on demand. Replay re-runs the exact stored flow from a declared initial state, and feeds the repair loop that turns a failure into a proposed fix.

Reproduce it on demand, not on a good day.

How it will be delivered

  • 01A branded IDEA Code-OSS distribution — a VS Code-family editor — with the Appvecta extension built in and sensible defaults already set.
  • 02Or your own VS CodeThe same extension runs in stock VS Code 1.103 or newer. The branded distribution adds branding and defaults; it never becomes required.
  • 03A local engineA process on your machine doing the real work — scanning, the project graph, agents, device control, QA and reports. The editor talks to it over JSON-RPC.
  • 04An appvecta CLIA small command-line tool for debugging and for running the same checks in CI.