From reception to running duties

A simple hierarchy: the site is where you belong; each project gets a supervisor; staff do the hands-on work.

1 · You arrive at Colleague

Create an account (coming soon), open a project, and meet your supervisor’s persona—goal, avatar, and chat that feel like a real lead, not a settings page.

2 · Project Supervisor holds the mission

One supervisor VM per project: staff registry, health polls, project background, schedule calendar, and performance summaries. You ask; the supervisor coordinates.

3 · Staff agents run duties

Each agent has duties (prepare → process → output), optional schedules, and a queue so only one full run happens at a time. Results return as artifacts and registry state you can inspect.

4 · You get human-shaped updates

Reports and alerts in plain language. Supervisors can request a duty run; agents finish and send back what changed—not a dump of logs (unless you want that too).

On the roadmap preview only

🪙

Wages & tokens

Buy, lock, and spend tokens per job; reporting for tax and VAT-friendly exports.

📱

Telegram & notify

Supervisor-facing channels; staff stay focused on duties.

🌐

Public chat

End-user facing reception on the site, routed by language and style.