JJETSYNGet in touch

Set up your COO

The COO is the chief AI employee: it holds your money goal and runs the rest of your AI team. Launch it with jetsyn coo from the command line, or open it in the web app. Set this one up first.

You do not hire a tool, you hire a chief. Every other AI employee on your team does one narrow job. The COO is the one that holds your money goal, decides what gets worked next, and points the whole team at it. Configure one chief, and the chief runs everything else.

What the COO is#

The COO is the chief AI employee in your workspace. It holds your goal (the number and the date you are working toward), reads your boards and your notes, and checks the live state of your work before it does anything. Then it plans, and it hands the work out to the rest of your AI employees. The COO manages. It does not do the line-work itself.

Set the COO up first. Skip it and you are hand-managing a dozen AI workers all day. Set it up and you manage one chief, and the chief manages them.

Launch it#

The COO is part of your Jetsyn workspace, so there is nothing to install per employee. You reach the same COO, in the same cell, two ways.

From the command line. The Jetsyn CLI is a full product, not a helper script. One command boots your chief, already attached to your task board and your goal:

bash
jetsyn coo

From the web app. Open your workspace and select the COO. It is the same employee and the same cell as the command line, just a different way in. Talk to it in plain words; it does the work and reports back.

Same chief, either surface

There is no separate CLI COO and web COO. jetsyn coo and the web app open the one COO over the one cell, so a goal you give it in the terminal and one you give it in the browser land in the same place.

Give it a goal#

Type your goal in plain English. The COO does not start guessing. First it grounds: it reads your goal and your notes, checks the live state of your work, and cites what it read. Then it writes a short plan and dispatches the work.

a goal you type to the COO
Audit the signup funnel end to end, fix the first broken step, and bring me a review-ready change. Money-first.

How one chief runs a team#

The COO never does the line-work. It writes one short plan listing the jobs, and runs them at once, then brings the results back as one report. The crew has four kinds of worker: recon scouts, assault builds, sapper fixes the plumbing, and medic reviews and heals.

When a run needs more workers than fit at once, or has to survive the COO itself restarting, it posts the jobs to a shared task board and launches each worker as its own program. They coordinate by claiming jobs off that board. The board is the proof the crew is live, not how many windows are open.

Verify it is live#

Do not take it on faith. Launch the COO and ask it to report its own tools back to you. If it lists the full set, including the team tools it uses to run the crew, your COO is live.

bash
jetsyn coo
> report every tool you have, then stop.

Where to go next#