VEZRYN
Menu
← All products

Graph

Community available

Engineering work,
coordinated.

From GitHub issues to implementation and pull-request delivery, with native Codex workers doing the engineering.

GET GRAPH COMMUNITY ↗Quickstart ↗

Open source · Apache-2.0 · Headless edition

Engineering delivery record

Tracked to date

Issues completed
—
Pull requests merged
—
Qualified repositories served
—

Qualified delivery and current repository enrollment are separate measures.

Last updated: unavailable

How we count

Figures count distinct source-qualified merged pull requests, separately verified completed issues, and repositories with qualified Graph source delivery from the reviewed cumulative source. Rolling snapshots are not added together.

Source evidence is currently unavailable.

Coverage and evidence qualifications follow the source report. These aggregates are separate from the recorded case study.

Delivery record unavailable.

OverviewHow It WorksTechnical Details

The overview

Give engineering work
a path to delivery.

Graph watches explicitly enrolled GitHub repositories and wakes a native Codex coordinator for actionable issues.

The input

A GitHub issue.

The original objective and repository context guide the work.

The engineering

Native Codex workers.

The coordinator delegates implementation in isolated worktrees and verifies changes.

The output

A reviewable pull request.

Implementation, verification, and delivery stay connected to the issue.

Graph at work

One objective. Multiple deliveries.

Read the existing reconstruction from private engineering records, with evidence and limitations explained.

Read the case study ↗

Graph Community is the public, headless edition. Vezryn’s private Graph system and private metrics are separate. Wednesday, the desktop workspace, remains in development.

The workflow

One continuous thread.
Clear engineering steps.

  1. 01 / Discover

    Find ready work.

    Watch enrolled repositories for actionable issues.

  2. 02 / Coordinate

    Scope and assign.

    A native Codex coordinator reads the issue and delegates workers.

  3. 03 / Implement

    Build and verify.

    Workers implement changes in isolated worktrees and run relevant checks.

  4. 04 / Deliver

    Return to GitHub.

    Carry the changes through the normal issue and pull-request lifecycle.

Graph workflow film · 2 minutes · Silent · Illustrative interface. An explanation of the workflow; the case study provides the evidence and limits.

Under the hood

Native workflows.
Inspectable source.

Graph Community coordinates engineering on your machine. It has no graphical desktop or hosted control plane.

GitHub issuesRepository watcherCodex coordinatorIsolated workersGitHub PR
Configuration
Explicit repository enrollment and editable Markdown playbooks, skills, and policies.
Execution
Native Codex coordination and workers in isolated Git worktrees.
Requirements & limits
Your own repository access and Codex entitlement are required. Platform qualification varies; review the current support notes before installation.
Authority
Graph is not an authorization boundary. Project instructions and review of agent actions still apply.