Quickstart: your team

Memnox on your machine governs the agent. Memnox Cloud governs the team around it. The first quickstart is the machine on its own, and this one is what a second person or a second machine makes possible: somebody who is not at the keyboard can answer an agent, see what every machine did, and change the rules once for all of them.

Most of this page happens in a browser, and nothing here requires anyone to write a line of configuration. One step is two commands on the machine the agents run on, for whoever runs them.

By the end, a machine will be answering to your workspace, Memnox will be reading two of your systems, will have proposed a decision it believes your team made, and you will have approved or rejected it.

1. Sign in

Open the console and sign in with Google. There is no password, by design: a credential nobody can lose is a credential nobody can leak.

What happens next depends on how your instance is configured:

• Your email is already provisioned. You land in your team's account with the role an admin gave you.
• Nobody has heard of you, and self-service is on. You get a new account of your own, never membership of somebody else's.
• Nobody has heard of you, and self-service is off. You are refused, and an admin has to add you first. See Roles and access.

2. Finish onboarding

The first time in, Memnox asks for the team name, what it does, and who you are. This is not decoration: the extraction step later uses it to tell a decision about your product from a decision about someone else's. An empty profile is the usual reason suggestions come back about somebody else's work.

3. Connect a machine

On the machine your agents run on, in this order:

memnox login
memnox setup

memnox login is the one deliberate step towards the cloud. A code appears in the terminal and a browser page asks you to approve the machine, naming it and the runtime version. On a server with no browser, --no-open prints the code and the URL instead.

memnox setup then does everything it does with no account, the interceptors, the edit hooks, the MCP proxy, a baseline of rules and the daemon, and because the machine is logged in it does one thing more. It offers each agent in turn, with what that agent can reach on screen, asks what the workspace should call it, and onboards it: the agent's configuration is backed up, one managed MCP entry is added to it, and the agent gets a credential of its own. Then it sends the scan to the console, so the agents appear there. Setup follows the control plane the account is on unless --url says otherwise.

Nothing about what an agent may do changes by being onboarded. That is still decided on the machine, and it keeps being decided there when the workspace cannot be reached. memnox logout forgets the credential and keeps the rules already pulled in force. The whole exchange is itemised on Connecting to a workspace.

4. Connect your first two systems

Go to Sources. Start with one system where the conversation happens and one where the work happens. One alone is not enough to show what Memnox is for, because a decision is usually made in one place and acted on in the other.

1. 1

   Pick a system and approve the consent screen

   You will be asked to allow access, in the tool's own words. None of them behaves differently here, because none of them has code of its own here. See Connected systems.

2. 2

   Choose what it listens to

   A connection on its own is quiet, and choosing what it listens to is what starts the flow. Subscribe where a decision might be visible rather than to everything the tool emits.

5. Watch events arrive

Open the workspace's Knowledge page. Within a minute or two of somebody sending a message or merging a pull request, it should appear, with a link back to the original.

6. Let Memnox propose a decision

Memnox reads the events and proposes candidate decisions, things it believes your team has decided and would want held to in future. This is the one step in the whole product that uses an LLM, and its output is a suggestion and nothing else.

7. Approve or reject it

This is the moment the product turns on. Approving records the decision, stamped with your name as the reviewer, and sends it to the runtime where it becomes a constraint agents are checked against.

Rejecting costs nothing. A rejected suggestion teaches Memnox what your team does not consider a decision.

8. Invite the people who will use it

Go to Members. There are three roles and the difference between them is what they may change, not what they may see. See Access and identity.

What to do next