Live at GDSC Hackathon · UMD · April 26

Every developer gets an AI coworker that actually knows them.

Autonomous Understanding & Behaviour Inference

AUBI reads your team's GitHub history and builds a persistent AI coworker for each developer. These coworkers know who owns what, share context with each other, and step in when something breaks — without anyone having to ask.

See it fix a bugMeet the coworkersWatch the mesh

The coworker mesh

Your team — as a living memory.

Each developer's GitHub history is turned into a Context Constitution — a structured memory of what they own, what they know, and how they work. These constitutions power the mesh.

O

Owner Coworker

Ownership Memory

ownsmatched code paths
ownsrecent commits
knowsRoutes incidents to the right developer profile using live constitution facts.
E

Expert Coworker

Adjacent Context

ownsrelated domains
ownsshared memory
knowsShares nearby context before code is read so fixes are not isolated guesses.
F

Fix Coworker

Patch Generation

ownsaffected files
ownstest commands
knowsReads the configured repository, drafts a patch, and feeds verification results back into memory.
P

PR Coworker

Approval Flow

ownsPR body
ownsissue linkage
knowsKeeps the human approval gate explicit before pushing changes back to GitHub.
Inspect full constitutions →
Use case · Live incidentRunning

Latest configured issue routed through AUBI memory

repo: configured target · AUBI routing through live memory

Open war room
✓

Issue Reader

✓

Ownership Router

Coworker Mesh

Fix Generator

PR Pusher

live

coworkers loaded from backend memory

0

Slack messages needed to route an issue

∞

memory facts per developer in Qdrant

90s

from GitHub issue open to merged PR

How it works

Coworkers consult. Bug gets fixed.

01
issue_reader
01

Issue opens

A GitHub issue drops. Something is broken in auth. Users are getting 401s.

◉
02
ownership_router
02

Right coworker found

AUBI checks who owns auth/ from commit history and constitution memory — no Slack needed.

◉
03
coworker_mesh
03

Coworkers consult each other

The mesh exchanges context from ownership, expertise, known issues, and shared team memory before a fix is generated.

◉
04
fix_generator
04

Fix generated

AUBI reads the actual code, writes the patch using shared team context, and runs the tests.

◉
05
pr_pusher
05

PR pushed

You approve. AUBI opens the PR on GitHub with full context — owner, fix, test results.

◉

Context Constitution

What each coworker remembers.

Built from real GitHub activity. Updated after every incident. No fake data, no self-reported profiles.

ownership

Which files and directories each developer owns, inferred from real commit history.

expertise

Languages, frameworks, and domains each person actually works in — not self-reported.

collaboration style

How they prefer to communicate. Used when drafting fixes and PR messages in their voice.

incident memory

After every resolved incident, the coworker learns. Future runs reuse that context.