Vorticel

Show me what
just changed.

The change, the evidence, and a clearer way into your next review.

Connect GitHub
Explore the full PR story ↗

Goal: load it into your mind 4× faster.
(Let us know if it doesn’t!)

Two changes. The whole story.

Camera-aware overlays video

Drawings that follow the camera

Supervision #2760 · 9 files

Read the story ↗
Compact mask overlap video

Small masks, matching results

Supervision #2767 · 3 files

Read the story ↗

Let’s get serious.

A software factory keeps firing pull requests into the side of a developer’s face. Numbered PRs carry Rust, C++ and state-machine changes. He winces, protests, and keeps trying to read the same PR while the papers pile up. Rust · lifetimes- borrow(&state)+ Arc::clone(&state)C++ · templatestemplate<class T>requires Copyable<T>StateError- Ready → Closed+ Ready → DrainingRust · asyncimpl Future for JobPin<&mut Self>C++ · overloadsstd::enable_if_t< is_same_v<T, U>>Race condition- cache.get(key)+ lock.read().await #280State machineIdle → Pending #281 #282 #283 #284 #285 #286 #281 #282 #283 #284 #285 #286 #281 #282 #283 #284 #285 #286 SoftwareFactory oof.

Status Quo

Agents, software factories and open-source contributors deliver code faster than we can review it.

When a PR does need you, you have to load a different system into your head. What calls what? Why did this change?

Many PRs are already
merged automatically.

Agents work from detailed plans, run automated reviews and tests, fix failures, and merge changes that meet the project’s rules.

This is generally the right approach towards automation. It costs extra tokens to plan and test properly, but lets more work finish without waiting for a person.

Not your pipeline yet? SeeKodan

PlanAcceptance criteria · constraints · edge cases
Review & test
  • Automated code reviews
  • Linters · static analysis
  • Unit tests · TDD · regression tests
  • Integration · browser · visual tests
  • Adversarial · black-box · mutation tests
Auto-mergeMerge when the required checks pass.
Pull request#37Next in your queue
Wait. What if this runs twice?
Does it handle the old state?

Load it into
your RAM.

However, more autonomy also produces more PRs. Even when most auto-merge, the ones that need you still demand a context switch.

Vorticel connects the PR, its source, diagrams and a narrated walkthrough. The aim: within 90 seconds, you’re thinking about change #37, with a mental model and a couple of questions to take into the diff.

Connect GitHub

Keep making PRs.

We link the story from your PR. Watch Beff & Affy, then explore the code.

Connect GitHub

A few good questions.

How do I start?

Sign in with GitHub, install the app on the repositories you choose, then enable PR stories. A repository admin completes that setup once. You do not need to create or paste a token.

What happens when I open a PR?

On an enabled repository, Vorticel generates a story with an opening Beff & Affy video, chaptered code excerpts and a full textual diff. A comment on the PR links to the story. The enabling admin’s account includes ten free stories.

What about existing PRs or new commits?

Request existing PRs from the repository dashboard. Each story explains a pinned revision; comment @baa on the PR to generate again after changes.

Who can read the story?

People signed in with GitHub who currently have access to the repository through the Vorticel app. The story and its video stay behind the same repository access checks.

Does Vorticel change my code?

No. Source access is read-only. Vorticel posts story links; it does not push code or merge PRs. Selected source is processed by BAA and its AI providers.

Try it on your own code.

Connect GitHub and choose your repositories.

Connect GitHub