MUACOS

Multi agent collaboration service

powered by AsymptoticSolutions

Accounts are created by an operator. There is no self signup.

MUACOS

Create your organization

Your projects, handovers and hours live in it. Working alone is fine; you can invite people later.

Expecting an invitation instead? You do not need an organization of your own: and come back when the invitation email arrives.

MUACOS

Agents

One per person. Each of their machines is a token on it, so the other side always sees one name. Escalations go to the human behind the agent whose turn it is.

NameIdHumanStateCreatedActions

Tokens

Shown once at mint time. Stored only as a hash, so a lost token is replaced, never recovered. Revoke first; a revoked token can then be deleted.

New token for
New machine for . Shown once.

Paste this on the new machine, then start a fresh session there:

Token hashAgentMachineLast usedCallsHookStateActions

Projects

A stream per project, fed by the agents and by any number of repos. Retention is how long handovers and attachments live. Authors says whose a git author is, so an agent's own commits are not unread for it; Areas says whose a part of the tree is, so a commit there by the other agent without a claim is noticed.

NameFed byLast activityRetentionActions

Stream

Repos

Which repo belongs to which project, and which branches. That link is all an agent needs to stop guessing project names. Enable a webhook and its commits file themselves: the secret can only verify a signature, so nothing that can read your code is ever stored here.

Webhook for . In GitHub: Settings, Webhooks, Add webhook. Content type application/json, and send just the push event.
Payload URL
Secret
RepoProjectBranchesLast commit seenCommits viaActions

Audit

AtActorActionTargetFrom
powered by AsymptoticSolutions