All projects

AI agent control plane

An internal workspace for agent jobs, instructions and run status.

Vue 3ConvexAgent runners
01

Challenge

Agent experiments become hard to track when prompts, runs and outputs live in separate places.

02

What we did

We created a control layer where tasks, agent context and run status sit in one real-time interface.

03

Result

The team can see what is running, what needs review and which agent workflows are reusable.

Dev-story article

AI agent control plane: how the project was built

Agent experiments become hard to operate when prompts, runs, outputs and review notes live in separate conversations. This project frames those pieces as an internal operations surface with traceable jobs.

Sections

06

Modules

04

Stack

Vue 3 + Convex

Duration: 12-15 min. From project to learning materials
01 00:00

Why the project exists

Agent experiments become hard to track when prompts, runs and outputs live in separate places.

Agent experiments become hard to operate when prompts, runs, outputs and review notes live in separate conversations. This project frames those pieces as an internal operations surface with traceable jobs.

02 01:00

What was built

We created a control layer where tasks, agent context and run status sit in one real-time interface.

The control plane gives the team a Vue and Convex workspace for defining agent jobs, storing task context, watching run status and reviewing outputs. It is designed around operational visibility rather than chat alone.

03 02:40

Main modules and user path

M01

The job queue records task instructions, owners, statuses and run metadata, so active and waiting work can be sorted without reading old conversations.

M02

Agent context records collect reusable instructions, working notes and input references for runs that should follow the same process more than once.

M03

Run status screens show queued, running, review and completed states in real time, making blocked or stale work visible.

M04

Review workflows capture outputs and follow-up decisions as records, so useful agent patterns can be repeated later.

04 04:30

Architecture and technology decisions

Technical foundation: Vue 3, Convex, Agent runners. This matters not as a logo list, but as the set of choices that keeps data, state, user actions and future maintenance manageable.

Vue 3 provides the operations surface and Convex stores live state. Agent runners remain outside the control plane, behind a clear job and status model.

05 06:30

How it works in a real scenario

In real use, “AI agent control plane” works as a clear sequence: it starts from the original problem, then the user takes the primary action, follows a clear data path and reaches the result. The experience stays logical instead of being a random set of screens.

The practical value shows where manual work used to be needed: part of the process is automated, responsibilities are clearly separated, and each module does one understandable job. That is what keeps the solution easy to maintain and extend.

06 08:30

Result and lessons

The team can see what is running, what needs review and which agent workflows are reusable.

The team can see what agents are doing, which results need review and which workflows are worth keeping. Agent work becomes easier to supervise and repeat.

Read next

These projects share nearby technical or product decisions, so they show how the same principle behaves in another context.

Have a similar idea?

Discuss your project