YAREMENKO
WORK
18:29
ALL WORK

OPERATOR CONSOLE

One console and four AI agents, each with one job. The agents do the routine work; I make the decisions.

YEAR
2026
ROLE
SOLOEND-TO-END
STATUS
LIVE

STACK

  • FRONTEND: Next.js 16 · React 19 · TypeScript · Tailwind 4
  • DATA: Supabase · Postgres · Auth with 2FA
  • AI: Hermes agent runtime · OpenAI models · custom Python tools
  • INTEGRATIONS: Notion · Telegram · Bright Data
  • INFRA: Docker · Caddy · VPS · GitHub Actions
  • QUALITY: Vitest · pytest
Operator console overview: today's briefing with the decisions waiting for the operator, the four agents online, today's run timeline, open tasks, server load and subscriptions, amounts redacted.Operator console overview: today's briefing with the decisions waiting for the operator, the four agents online, today's run timeline, open tasks, server load and subscriptions, amounts redacted.
COMMAND SURFACE

CONTEXT

I run a solo studio: client work, my own products, freelance briefs and the posts that keep the studio visible. Writing code was never the slow part. Reading everything that comes in and deciding what needs an answer was.

02 / PROBLEM

Every tool held one piece of the picture, and none could see the others. I was the link between them, and on a busy week that is the first thing to break.

I built all of it alone: the product idea, the database, the agents and their tools, the design system and every screen.

MY ROLE

SOLUTION

One console, and four agents that each own one job: Aster coordinates, Solomiia reads freelance leads, Echo drafts posts, and Leo teaches me whatever I am learning.

  1. 01

    The agents do the legwork. They check the freelance exchange every half hour and read the news three times a day. Nothing waits for me to go looking.

  2. 02

    Solomiia reads each lead before I see it: what the client wants, how well it fits, the risks, and a draft reply. Echo turns the week's work into post drafts in two languages.

  3. 03

    Only decisions reach me. Telegram brings just the cards that need a person: approve, decline or reply.

  4. 04

    One database and one schedule for everything. Every agent job has its run history, and the console warns me when something breaks.

  5. 05

    It all runs on my own server, on fixed monthly plans instead of pay-per-use. Each client would get their own copy, so no one's data sits next to anyone else's.

WHERE IT STANDS

I use it every day. The morning starts on the overview: what the agents found overnight, what they already turned down and why, and the few decisions that are mine. Freelance leads and content go through it end to end.

IN NUMBERS · OCT 2026

freelance leads
317
news items collected
800+
post drafts
100+
agent actions logged
10,000+