Every project's agent list contains two kinds of agents.
Platform agents
Marked Platform on the dashboard's workspace agent settings — also described as "has access to all projects". The backend automatically includes Platform agents in every project's agent list, so you don't have to assign them one-by-one.
Typical Platform agents:
- A general-purpose developer agent that does most coding work.
- An infra/operations agent that handles deploys, observability tasks, etc.
- A reviewer agent that audits other agents' PRs.
When a Platform agent is added on the dashboard, every project's local Build Station settings gain that agent on the next resync. Build Station enables it by default — Platform means "should be active everywhere".
Project agents
Explicitly assigned to a specific project on the dashboard. These show up only in that project's agent list — not across the workspace.
Typical use:
- A specialized agent only needed for one project (e.g., a "frontend-only" agent on a UI repo).
- An external consultant agent given access to one customer project.
- An experimental agent you're trialling in a sandbox project before promoting workspace-wide.
When you assign a project agent on the dashboard and resync, it appears in the project detail panel. Build Station also enables it by default (the assumption is: if you put it on this project, you want it active here).
Why the distinction matters
For your day-to-day usage, it mostly doesn't — both kinds work identically. But there are a few places it surfaces:
- Auto re-enable behavior on resync. Platform agents that have
enabled: falselocally are flipped back totrueon resync. Non-platform user-disabled agents stay as you set them. - Workspace-wide visibility. Platform agents appear in every project, even ones you haven't worked in yet. Project agents only appear in their project.
- Disabling. You can disable a Platform agent on a specific project on this Build Station and your choice will be respected (until the next manual override). For project agents, disabling here just means "don't run it on this machine".
Identifying which is which
In the project detail panel, each agent shows a small Platform badge if applicable.
On the Meshly Build dashboard, the workspace's agent management page lists Platform agents with a "Platform" tag and "has access to all projects" caption.
Why a Platform agent might be missing on a project
A few possibilities:
1. Project was created before the agent
The backend adds Platform agents on the next sync after the agent gains Platform status. Resync the project to pull it in.
2. The agent was excluded server-side
Workspace admins can opt specific projects out of a Platform agent. Check the dashboard.
3. Local cache is stale
Rare, but possible if Build Station crashed mid-resync. Manually click Resync on the project.
What "enabled" means for each
Same thing! Enable / disable on Build Station just controls whether this machine runs tasks for that agent. The server-side existence of the agent and its identity are untouched either way.