Desktop Execution Manager
Run an Erebine Execution Manager (EEM) inside the Erebine desktop app. It enrolls to your project and serves code workspaces that point at folders on this Mac.
Overview
The Execution Manager is a context in the desktop app. Its EEM destination hosts an EEM in the app's own process: no container, no install step. The EEM belongs to the project you are signed in to, and it serves only the code workspaces it declares. The sidebar lists it in the Advanced experience.
The EEM can only touch the repository roots its declared workspaces name. A Mac runs the code tools and git; the Linux infrastructure tools are not available here. For those, deploy an EEM on a Linux host, see Deploy Your First EEM.
Code, in the same app, does not use the EEM. It runs its tools in the app, in a folder you open, and registers nothing in the project.
Enroll This Mac
Open EEM in the sidebar. Until the EEM is set up, the pane shows three cards and an Enroll & Start button.
- Sign in and choose a project. The Requirements card checks Signed in with a project.
- In the Join key card, press Mint a join key, or paste a key. Minting creates this Mac's EEM in your project. The key is kept in your Keychain until this Mac enrolls with it, then discarded.
- Optionally set EEM name. The name is used when this Mac enrolls; changing it later does not rename the EEM.
- Press Add workspace to declare a code workspace (next section). The EEM enrolls without one, but every code tool refuses until a workspace names a folder on this Mac.
- Press Enroll & Start. It is enabled once a join key is in hand.
After enrollment the pane becomes a dashboard: the EEM's state, its Readiness (Enrolled, Router token, Manifest loaded, Lease acknowledged) and what it Advertised. A relaunch resumes from the saved enrollment, so starting again needs no key.
Code Workspaces
Open the workspaces sheet with Add workspace (before enrollment) or Edit workspaces (on the dashboard), then choose New code workspace.
- Press Choose folder and pick the folder the code tools may read, edit and build. It becomes the workspace's repository root.
- Enter a Name: lowercase letters, digits and hyphens, at most 48 characters. The name must be new in the project.
- Press Create. The app creates the operational workspace in your project and declares it on this EEM.
- Press Save. Nothing is written to this Mac until you save. Saved changes take effect without a restart.
A workspace no chat is linked to runs nothing. The new workspace offers Link a chat...: choose the chat whose tool calls should run there. See Connect a Chat to an EEM.
Add from this project declares a workspace that already exists in the project.
A declared workspace's Types lists the
types this Mac can serve. Choose one or more: each adds
its scope fields to the form and suggests a credential
family. Under Credentials, each row names
a file you place in the workspace's folder in the EEM's
credentials directory; Add credential
binds another family a tool reads: kubernetes,
openstack or git_token. A
workspace that already binds another family shows it
with a note: no tool reads that file yet, so tools of
that family are refused in the workspace. Remove the row
to unbind it. The secret stays in that file and is never
entered in the app.
A workspaces file written before a workspace could have several types opens with a note for each declaration it read in the old shape. A type or name Erebine does not recognise is marked, with the rule it breaks; correct it and press Save, which writes the whole file in the current shape.
Allow autonomous trust on a workspace is
this Mac's half of
autonomous trust:
once the project's owner also turns the trust on for the
workspace, its calls run with no person approving them,
except irreversible and database
calls. It is off by default and takes effect when you save.
Where Things Live
| What | Where |
|---|---|
| Declared workspaces | ~/.config/erebine/workspaces.yaml by default; the Workspaces file field changes it. The EEM reads it on every tool call. |
| Enrollment, keys, queued dispatches | ~/.local/state/erebine/ |
| Join key before enrollment | Your Keychain, until this Mac enrolls with it. |
Stop, Re-enroll and Forget
Stop halts the EEM and keeps its identity. Start resumes from the saved enrollment.
Re-enroll, offered while the EEM is stopped, discards this Mac's saved enrollment, enrolls with a new join key and starts again. The signing and CURVE identity the router already knows is kept. Signed in, the Join key card offers Mint a join key here too, minting into the project you are signed in to; that is how a Mac whose saved enrollment belongs to another project moves its EEM to the one it is signed in to now.
Forget asks Forget this Mac's execution identity? It stops the EEM and deletes its enrollment, its signing key, its CURVE key and its queued dispatches from this Mac. The next start enrolls as a new EEM with a new identity. Signed in, it also deletes the EEM from your project. Signed out, the EEM stays in the project; sign in and press Forget again to remove it.