CASE STUDY

Running Many Projects and AI Agents from One Screen and Your Phone: Our In-House Tool cockpit

Overview

cockpit is a tool we built ourselves to run AI agents working on many projects at the same time, all from one screen and a phone.

Overview of cockpit. On the left, projects A, B and C each have AI agents at work. In the middle, the cockpit screen lists every agent in one place. On the right, a phone receives a "Needs approval" notification with Allow and Reply buttons.

The problem

  • In the way we work, Cursor and VS Code were heavy: running several projects and agents at once kept freezing the PC
  • With many projects, when an AI stopped to ask "May I run this?", we couldn't tell which project or agent it was
  • We wanted to see what every agent was doing at a glance

What cockpit does

How a stopped agent gets moving again: 1 working, 2 stops (needs approval or has a question), 3 rises to the top of the screen and pings your phone, 4 one tap to allow or reply, 5 back to work.
  • Everything on one screen — the agents at work, grouped by project
  • Stopped ones rise to the top — only the agents waiting for a person collect at the top, automatically
  • One tap on your phone — allow or reply straight from the notification, so work keeps moving even when you're out
  • Request box — send a request from your phone mid-meeting, and the next free agent picks it up

We built it as our own screen that runs in a browser, without relying on editor products such as Cursor or VS Code. An editor above the terminal shows each change on the spot, so the AI's work and the human check sit in one place.

The actual screens

On a computer, files, code, the terminal and the list of AI agents share one screen. Anything waiting for a person collects under "Needs attention" at the top right.

cockpit on a computer. Files on the left, code and the terminal in the middle, the list of AI agents on the right. Under "Needs attention" at the top right: project A waiting for approval (with Allow and Deny buttons) and project B waiting for input.

On a phone, too, whatever needs attention sits at the top, and you can allow or reply right there.

cockpit on a phone. Under "2 need attention": project A waiting for approval (Allow, Deny, Open) and project B waiting for input (Reply), followed by the agents at work.

The screens were captured with demo projects.

Connected to projectAI

How agents connect to projectAI tasks. Each agent checks its projectAI task before starting, then records progress, time spent and pull requests in projectAI. Who is working on what is visible in projectAI.

Each agent works against a task in projectAI, our own project management tool. It checks the task before starting, then records progress, time spent and pull requests in projectAI.

Results — all from one development machine

Every figure below comes from one of our development machines, over about the last two months.

cockpit in numbers, all from one of our development machines (about the last two months): up to 28 AI agents at once (23 of them helper agents); up to 9 projects in parallel in a day; 15 projects; 144 working sessions; about 100,000 AI responses; about 57,000 tool runs; about 386 hours of agent work.

They are counted from the AI agents' work logs, treating any stretch with no gap longer than ten minutes as "running", and include helper agents called in along the way.

Interested in cockpit?

If your company is interested in how cockpit works, or in setting up development with several AI agents, we'd be glad to hear from you.

Related case studies and services

SERVICES

Services Related to This Case Study