awww

Our Works 01

Aware

An editor where you lead a team of agents.

Get early access
Aware: code on the left, Captain's chat on the right, Maper's agent timeline at the bottom context graph captain maper 3 agents, 6 of 6 tests
i.

Pair coding, not autopilot

Good software has always been made in pairs: one person at the keyboard, one person thinking a step ahead. Aware keeps that shape. The agents write, run and fix. You set the intent, read the plan and decide what ships.

Turn Intent up and Captain asks before it builds. Turn Micromanage on and you call every shot while Captain does the typing.

Intent: from Off to Deeper, plus Micromanage: Lightly, Closely, Obsessively
Captain modes: Ask, Build, Team
ii.

A hierarchy of agents

One agent trying to do everything loses track of what it was doing. Aware splits the work the way a good team does.

  1. YouThe intent. What should exist, and why.
  2. CaptainPlans, splits the work, hands it out and reviews what comes back. It does not write the code itself.
  3. WorkersEach takes one task in the shared workspace and raises its change. Captain merges only what passes.
Captain splits a login task across three workers, then runs the tests: 6 pass, 0 fail
TeamChat: Nova, Atlas and Pixel report their progress in one thread
iii.

Watch it work

Maper replays every run: who was spawned, what each agent was asked to do, and when it finished. Nothing happens off the record.

iv.

Aware One

One quiet view for when you just want to say what to build. The whole team is still behind it.

Aware One: What should we build in aware-demo-login?