Glossary

Agent

The AI assistant that carries out a task. Vyazen supports multiple models; an agent can spawn subagents (e.g., an "explore" subagent) to look things up.

Approval gate

A point in the workflow where the agent pauses and waits for you — to answer a question, approve a design, or approve a pull request. Nothing is committed without your approval.

Branch

A Git branch within a connected repository. The branch is the workspace where a task's changes are made; the agent commits to it.

Code graph

The searchable map Vyazen builds of your repository — structure (files/projects), symbols (classes/functions), the links between them (calls, imports, type usage), and AI summaries. Powers the agent's code awareness, code search, and the wiki. Also called the index.

Database

A Postgres database you connect to visualize its schema as a graph. See Databases.

Instance

A sandboxed environment Vyazen provisions to run exactly one task's agent. Has a lifecycle: provisioning → ready → running → terminated, or failed.

Integration

A connection to an external service — a source-control manager (GitHub, GitLab, Bitbucket) for connecting repositories, or an OAuth provider for sign-in. See Integrations.

Index

Another name for the code graph — the searchable understanding Vyazen builds of your repository.

Model

The AI model that powers an agent. Different models may be used for different workflow phases; which are available depends on your instance's configuration.

Repository

A source repository you connect to Vyazen, scoped to a branch. Tasks run against a repository + branch.

Skill

A bundled agent capability — e.g., planning an implementation step-by-step, or reviewing its own work. Skills make the agent follow a disciplined process.

Subagent

A lightweight agent the main agent spawns for a sub-task, such as querying the code graph (an "explore" subagent).

Task

A unit of engineering work scoped to a repository and branch. You create a task with a description; Vyazen runs an agent to complete it.

Wiki

The auto-generated documentation Vyazen produces for a repository — pages like Overview, Architecture, and Glossary — which you can also chat with. See The code wiki.

Workflow

The structured sequence of phases a task moves through: research → clarify → design → plan → implement → verify → review → pull request. Not every task runs every phase, but research, verification, and a PR are always present.