# Use a project from another machine

`npx brynth init` creates a new project. To use an existing one from a second machine, bring a key, not the admin credentials.

## 1. Create a key on the first machine

`--platform` must name the client that will use the key: the skill's `session_hello` sends that client's name, and a key fixed to another platform keeps its identity and returns an `IDENTITY_CONFLICT` warning, so the ledger would record the wrong client. For Claude Code:

```bash
npx brynth key create --scopes inbox:read,inbox:write,send,disk,approvals,ledger:read --platform claude-code --label laptop-2
```

For Codex:

```bash
npx brynth key create --scopes inbox:read,inbox:write,send,disk,approvals,ledger:read --platform codex --label laptop-2
```

The token is printed once. Move it with a password manager, not by chat or email. Add `admin` to the scopes only if the agent there must add sources or keys. `--platform` alone sets the agent name too (lower-cased); `--agent` needs `--platform`. Without either, the first `session_hello` sets the key's identity. Create one key per client: two clients on the same machine need two keys.

## 2. Connect the client on the second machine

From the project folder, with the key created for that client:

```bash
BRYNTH_KEY=brk_live_… npx brynth connect claude-code
npx brynth skill install --client claude-code
```

For Codex, `connect codex` and `skill install --client codex`, with the Codex key.

With `BRYNTH_KEY` set, `connect` creates no key and writes nothing to `credentials.json`: it writes the key of the environment into the client configuration. It does not install the skill, hence the second command; without `--client`, a machine with no saved project gets the skill for both clients.

`BRYNTH_KEY=brk_live_… npx brynth status` shows the project with that key; sections the key cannot read say which scope they need.

## 3. Revoke when done

On the first machine, `npx brynth status --json` lists the active keys with their ids. Revoke one with `DELETE /v1/keys/{id}` and the admin key (see [REST](/reference/rest.md)).

Signing in to an existing project from the CLI, without a key, is not available yet.