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 workspace, an owner accepts it, and only then is it offered to agents. 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 owner, accept it — nothing reaches an agent before a person accepts it.
Point your agent at the GitMir MCP server and let it take the next task.
Read what it reported back, next to what the task promised.
GitMir does not execute anything. There is no GitMir Compute in the product today — nothing here runs code, edits a file, opens a pull request or calls your CI. The writing is done by your own agent or your own developer, in your runtime, under your permissions. Taking and closing work happens only over MCP; the workspace has the screens for writing it, accepting it and reading the result. The one thing GitMir runs by itself is reading your repository to build or update the model.
Three models are published in full and open without an account. Ask one of them the question this page is about.