Skip to content

docs(changelog): tag-based runner placement (Jun 06) #80

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
indykish merged 3 commits into from
Jun 6, 2026
Merged

docs(changelog): tag-based runner placement (Jun 06) #80

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
495b394
docs(changelog): add tag-based runner placement entry (Jun 06)
indykish Jun 6, 2026
8c09699
docs(changelog): disambiguate tag limits, note silent runner wait
indykish Jun 6, 2026
76d0e7b
docs(api): drop dead agent-memories nav entries
indykish Jun 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions changelog.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,22 @@ export const STAGE_SELF_MANAGED_M66 = "$0.0001";
usezombie is in **stealth-mode testing** and pre-production. APIs and agent behavior may change between releases without long deprecation windows. Email [usezombie@agentmail.to](mailto:usezombie@agentmail.to) if you want a hand calibrating an agent or to join as a design partner.
</Tip>

<Update label="Jun 06, 2026" tags={["What's new", "API"]}>
## Pin an agent to capable runners with tags

An agent's `tags:` now decide where it runs. Add `tags: [gpu, us-east]` to your SKILL.md frontmatter and the agent runs only on a runner whose advertised labels cover every tag — capability-bound work lands on a host that can serve it. An agent with no tags runs on any runner, exactly as before. The tags you already write in the manifest drive this; there is no separate field to set.

If no enrolled runner currently advertises the required labels, the agent waits for a matching runner rather than running on an unsuitable host.
Comment thread
greptile-apps[bot] marked this conversation as resolved.

<Note>
A waiting agent surfaces no separate status today. If an agent never starts, confirm an enrolled runner advertises every tag the agent requires.
</Note>

## API reference

- **`required_tags` on an agent** — derived from the SKILL.md `tags:` on create and re-derived when you `PATCH` a new `source_markdown`. A runner claims an agent only when `required_tags` is a subset of the runner's labels. Each tag is 1–64 characters; an agent carries at most 32. Either bound exceeded rejects the request with `UZ-REQ-001`.
</Update>

<Update label="Jun 04, 2026" tags={["Breaking", "What's new", "UI", "CLI", "Security"]}>
## Enroll runners from the dashboard, plus a regrouped left navigation

Expand Down
4 changes: 1 addition & 3 deletions docs.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -196,9 +196,7 @@
{
"group": "Agent memories",
"pages": [
"GET /v1/workspaces/{workspace_id}/zombies/{zombie_id}/memories",
"POST /v1/workspaces/{workspace_id}/zombies/{zombie_id}/memories",
"DELETE /v1/workspaces/{workspace_id}/zombies/{zombie_id}/memories/{memory_key}"
"GET /v1/workspaces/{workspace_id}/zombies/{zombie_id}/memories"
]
},
{
Expand Down
Loading