Not a Rabbit. Don't Follow Trails: The Story Behind Our AWS Summit Sticker

If you picked up a black sticker at AWS Summit with the words "Not a Rabbit. Don't follow trails." on it, this post is the long version of what is printed on that sticker.

It is also, more importantly, the short version of how we think about code review at Octopus.

The five words on the sticker

We did not put a logo on the sticker. We did not put a QR code, a website, or a call to action. Just five words and a small octopus.

That was on purpose. A sticker that screams "scan me" gets pulled off a laptop in a week. A sticker that quietly says something the owner agrees with stays on the laptop for a year. We wanted the second one.

The phrase itself, though, is not just decoration. It is the entire product thesis compressed into five words.

What "following trails" means in code review

Most code review tools, human and AI alike, behave like rabbits.

A rabbit is a perfectly good animal. It is fast, it commits, and it follows a single trail. When you give it a pull request, it does what a rabbit does: it looks at the diff, it reads the few files the diff touches, and it starts running down whatever trail is in front of it.

Inside that trail it is sharp. It will catch a typo, a wrong type, a missing null check. But the trail is narrow by definition. The rabbit cannot see:

• The function you renamed is called from a service that is not in this PR.
• The migration you wrote violates an invariant inside a worker queue you have never opened.
• The new permission check silently duplicates a guard that already exists three folders away.
• The util you added was already written, slightly differently, two years ago by someone who has since left the company.

These are not edge cases. These are the bugs that ship. They are the bugs that get caught in incident review at 2am, not in code review at 2pm. They are also the bugs that no rabbit, no matter how fast, will ever find. Because finding them requires looking somewhere other than the trail in front of you.

What an octopus does instead

An octopus does not pick a trail. It wraps around an object and senses it from every angle at the same time. Eight arms, around two thirds of its neurons distributed across those arms, and a central brain that pulls all of it together. It is, in a literal biological sense, a distributed system.

That is the model we built Octopus on.

Before Octopus reviews a single line of your pull request, it indexes your whole repository. Every file, every function, every cross-reference. It builds a semantic map. Then, when a PR comes in, it does not just read the diff. It reviews the diff against the map.

The result is a different kind of comment. Instead of:

"Consider adding a null check on user."

You get:

"This branch is unreachable, because getUserById already throws on null at services/users.ts:42. The check above shadows that error."

That second comment is not possible without seeing the rest of the codebase. A rabbit cannot write it. An octopus can.

Why we picked AWS Summit

AWS Summit is full of people who know exactly what we are talking about, even if they would not phrase it this way. They have all reviewed code that looked fine in isolation and broke something a thousand lines away. They have all merged a PR that passed every check and woke them up at 3am.

The sticker is for those people. If "Not a Rabbit. Don't follow trails." made you smile, or made you tilt your head, or made you Google it, you are exactly who we built this for.

The product, in one paragraph

Octopus is an open source, self-hostable, AI code reviewer that indexes your full repository and reviews every pull request with that full context in memory. It is not faster because it skips work. It is better because it does not have to guess what the surrounding code looks like. It runs as a GitHub App, a GitLab integration, or a CLI you can drop into any pipeline. It is free to self-host, and the hosted version starts free.

If the sticker brought you here, the easiest next step is to spend ten minutes on octopus-review.ai and see what a non-rabbit review looks like on a real PR.

One last thing

The sticker is a small object with a small idea on it. But the idea behind it is not small. Code review that only looks at the diff is the dominant pattern in our industry, and it is wrong, and it has been wrong for a long time. We are not the only people pointing this out, but we did make the best sticker about it.

Thanks for reading. And thanks for keeping the sticker on your laptop.

Don't follow trails.