Use this guide for basic terminal work on the Integration Server: reconnect, inspect your project, check sign-in and recover onboarding. For first access, use Developer workstation setup. The downloaded client normally prepares the workspace for you.
This workspace supports the AI Fabrix operating model: build governed integrations and Role Assistants, then retain proof of their behavior.
Prerequisites
- Developer access and completed client enrolment for the installation.
- The SSH alias and project path printed by the client.
- Your company and coding-provider accounts; GitHub access when using a remote repository.
The Integration Server supplies Node, Git, GitHub CLI, tmux, Builder CLI, Claude and Codex. You do not install those tools for each project. Docker and administrator privileges are not available to workspace users.
Where it lives
With the HTTPS transport, your SSH session travels through an authenticated WebSocket tunnel over HTTPS on port 443. The AI Fabrix client uses your organization’s SSO sign-in, such as Microsoft Entra ID, to authorize the connection. Access depends on your current developer entitlement; the server does not need a publicly exposed SSH port.
Run ssh aifabrix from your computer using the connection entry created by the client. That entry starts the HTTPS tunnel automatically. Run the remaining commands in the remote shell. Your project, Agent Kit files and coding sessions stay on the Integration Server.
Keep projects under the managed work directory. Do not edit the provisioned Controller address or managed configuration by hand: the server synchronizes those settings. Use the project path printed for your installation rather than assuming every workspace has the same directory.
How to set
Connect and inspect
From your computer:
ssh aifabrix
Substitute the printed alias if you have multiple installations. Once connected:
pwd
ls
af help
af auth status
af help explains onboarding and the platform addresses. For flags on one command, use af onboarding --help. Change into the project directory printed by the client before running project commands.
Check your Git identity
On the workspace, inspect the identity used for commits:
git config --get user.name
git config --get user.email
If missing or incorrect, set your approved identity:
git config --global user.name "Your Name"
git config --global user.email "you@example.com"
A GitHub sign-in and a Git commit identity serve different purposes. Verify both when you intend to commit and push.
Recover or change onboarding
Usually, rerunning the downloaded client is enough. If the workspace tools predate guided setup, or you need interactive recovery in SSH, run:
af onboarding
It reads managed configuration and reuses the workspace. For a deliberate client or workspace change:
af onboarding --coding claude
af onboarding --coding codex
af onboarding --name sales-workspace
If managed configuration has no codingPlatform, the first explicit
--coding choice is saved so a later run can omit the flag. If a default is
already configured, --coding selects another platform for this run without
replacing that default. Claude uses a detached tmux session; Codex opens through
its own remote-project interface. Cursor does not need a runtime on the
Integration Server. Connect with SSH and open the project in the Cursor desktop
app on your computer.
Interactive af onboarding --repo owner/name can clone a repository or create it privately and push an initial commit. Use it only when those remote actions are intended. This differs from the downloaded client's guided repository-selection flow, which does not create or push repositories.
Defaults and examples
| Task on the workspace | Command |
|---|---|
| Inspect project changes | git status |
| Inspect Agent Kit | af agent-kit status |
| Validate Agent Kit | af agent-kit validate |
| List running coding sessions | af agent-kit list |
| Check GitHub sign-in | gh auth status |
Follow the printed command to attach to an existing Claude session. Detach from tmux with Ctrl+b, then d; detaching leaves the session running. For Codex, select the remote connection and project in your local app. For Cursor, connect with SSH and open the project in the Cursor desktop app on your computer.
If a vendor sign-in expires, rerun the downloaded client, or use the relevant remote command: gh auth login, claude auth login, or codex login --device-auth. These sign-ins are separate from af auth status.
Validate
Confirm the intended Controller and environment in af auth status, the correct directory with pwd, and the expected project changes with git status. Agent Kit validation checks project tooling; it does not establish that your integration is correct.
After recovery, reopen the same project and check the failed step again. Retain the command, error and installation name when asking for help, without copying tokens or credentials.
Common mistakes
| Symptom | Next action |
|---|---|
| Missing managed configuration | Confirm you are in the remote workspace; ask the administrator to repair provisioning |
| Git commit identity missing | Set your approved name and email on the workspace |
| Permission denied during SSH | Ask the administrator to check access and enrolment |
| Need system-wide software | Ask the administrator to update the workspace image |
| Coding session appears lost | Inspect sessions and use the printed attach command |
Limits
These instructions cover a managed Integration Server workspace. Portable setup on an unmanaged machine has different prerequisites; see CLI reference. Installing platform containers is a separate task described in Set up a local platform. Retain your organization's review and certification gates before publishing integration work.