Runtime
The machine where agents actually execute. Comparable to a TeamCity agent or GitHub runner. The platform sees availability, current load, running processes, and related artifacts.
loadqueueagentsenvironment
A shared process emerges when the team has shared entities that can be referenced, granted permissions, assigned tasks, and measured.
The machine where agents actually execute. Comparable to a TeamCity agent or GitHub runner. The platform sees availability, current load, running processes, and related artifacts.
A named digital executor with a model, harness, instructions, skills, tools, permissions, and project context. At an advanced level, a whole pipeline—such as a planner, developer, and reviewer—can sit behind one Agent while remaining a single task executor from the outside. In the current implementation, the configuration is tied to a runtime.
A logical, reusable capability. For example: finding the right Unity prefab, visually verifying a result, reviewing code, or following project conventions. Several agents can use the same skill version.
A unit of agent work. It contains the brief, executor, status, comments, queue, multiple execution attempts, and the materials used to accept or reject the result.
Runtime provides the execution environment, Agent defines the digital executor and its pipeline, Skills add reusable capabilities, and Issue stores the brief and work state. A particular execution connects these entities and creates a shared history.
This is why a run leaves behind more than code. The Issue collects the plan, summary, changed files, commands and logs, screenshots, test results, final report, and execution trace. Metrics sit beside them: time, tokens, model, runtime, attempt count, errors, rejections, and estimated cost of the accepted result.
If one run was not enough, the conversation continues within the Issue context. QA can ask about regression risk, a developer about the prefab choice, and a lead about a decision in the plan. The agent answers as the actual executor, not as a hidden function behind a developer acting as intermediary.
Ordinary chat remains available for quick questions: it lets someone contact a project agent without the full Issue process or mandatory generation of every artifact.