← All docs
Getting started
Your first sessionThe workspaceSSH access
Core concepts
Agent rolesExperimentsResearch plansCanvasWorkflows
Integrations
GitHubWebhooksNotifications
Platform
Billing and plansAgent memoryMulti-chatKeyboard shortcuts
Reference
GPU catalogAgent toolsAPI referenceSecurityLimits and quotas
← Docs
Core concepts

Agent roles

The five roles

Every Meshia session starts with one agent. You can hire additional agents, each with a specialized role:

| Role | What it does |

|---|---|

| Researcher | Reads papers, builds hypotheses, designs experiments, writes literature reviews |

| Coder | Writes and debugs code, sets up environments, manages dependencies, optimizes training loops |

| Reviewer | Reviews code and experiment results, catches bugs, suggests improvements, validates methodology |

| Data | Handles datasets. Downloading, preprocessing, augmentation, splits, format conversion |

| Ops | Manages infrastructure. Monitoring, logging, checkpointing, scheduling, cleanup |

Hiring and firing

Click the + button next to the agent roster in the right panel to hire a new agent. Pick its role from the dropdown. The agent spins up immediately and joins your session's shared context.

To remove an agent, click its avatar and select Dismiss. Its work stays in the session. Only the agent is removed.

When to use which

Solo work: One Coder agent handles most single-task jobs. Fine-tuning a model, running a script, setting up an environment.

Research projects: Start with a Researcher to plan the experiment, then hire a Coder to implement it. Add a Reviewer before committing to a final approach.

Data-heavy pipelines: A Data agent plus a Coder is the typical pairing. Data handles acquisition and preprocessing; Coder handles the training loop.

Production prep: An Ops agent watches resource usage, sets up checkpointing, and handles the cleanup you'd forget to do yourself.

How roles affect behavior

Each role has a tuned system prompt that shapes its priorities and tool usage. A Researcher will default to reading and planning before executing. A Coder will default to writing and running code. You can always override this (tell a Researcher to write code and it will), but the defaults match the role's strength.

Agents in the same session share a blackboard. They can see each other's messages and outputs. You don't need to relay information between them.

← SSH accessExperiments →