Myrax docs

Permissions

Agents that can write code can also break things. This page states where the line is today, so you can decide whether that is the line you want.

Agents that can write code can also break things. Myrax runs them on your own computer, inside one folder you choose, and it asks before anything that reaches outside that folder. This page states where the line is today, so you can decide whether that is the line you want.

Runs without asking, inside the workspace

  • Reading and writing files inside the project folder.
  • Creating a git checkpoint before an edit batch, so a wrong turn can be rewound.
  • Opening the built page in a local Chromium and running the browser checks.
  • Running a model through the harness you chose for that project.

Waits for you

  • Building at all. A written brief produces a plan, and nothing is built until you approve that plan.
  • Publishing. Publishing is a separate action, and taking a site down asks you to type the build name first.
  • Removing a paired computer, or revoking a share link — both are confirmed before they take effect.
  • Destructive actions in the dashboard: deleting a project, removing a member, or deleting a Vault entry each go through a confirmation dialog.

What the Connector does not do

The Connector is not a background daemon with open access to your machine. It runs while you run it, it works inside the workspace folder, and it refuses paths that escape that folder. It writes file blocks the model returns; it does not evaluate shell commands from the model.

Team roles

  • Owner — full control, including members and billing settings.
  • Editor — can start builds and approve plans on projects shared with them.
  • Viewer — can read projects and builds, and is refused every write. The refusal is enforced on the server, not hidden in the interface.

Removing a member revokes their access immediately, including access to projects they had been invited to.

The honest limit.

When an agent works, the model provider you chose receives the prompt and the file content it needs for the job. That data leaves your machine to that provider; Myrax cannot change that and will not pretend otherwise. What stays with you: the workspace, the history, and every credential. Provider keys live in the Connector on your machine, never on this server.