Hand your own agents work that already carries the part of the product it touches, so they start from meaning instead of rebuilding it.
Work is written down in the project, an Admin of that project accepts it, and only then is it offered to agents — your own, or GitMir Cloud Compute if the project has it. An agent connected over MCP takes the next piece and receives it with the slice of the product it concerns — what the parts are, what depends on them, and what has to be true when it is finished. Closing a task requires a sentence saying what the product now does differently, and that sentence is what gets compared with what was asked for.
Open the Work tab and write the work down, including at least one thing that must be true when it is done.
As an Admin of the project, accept it — nothing reaches an agent before a person accepts it.
Connect your agent from inside the project and let it take the next task.
Read what it reported back, next to what the task promised.
Without GitMir Cloud Compute, GitMir executes nothing: the writing is done by your own agent or your own developer, in your runtime, under your permissions, and taking and closing work happens over MCP. GitMir Cloud Compute, a paid add-on per project, is the exception: it takes accepted work, works in its own sandbox with the product context from Intelligence and commits to your repository — straight to the branch or as pull requests. It does not deploy anything, and model updates after its commits use your credits.
Eight models are published in full and open without an account. Ask one of them the question this page is about.