Start with your organization's Integration Server download page. The AI Fabrix client signs you in and prepares a remote coding project; the Integration Server supplies the development tools and managed workspace.
You work in that workspace through Claude or Codex. Your computer runs the connection client and, for Codex desktop use, the Codex app. You do not need to install Node, Builder CLI, Git or Docker locally to complete this onboarding.
Prerequisites
- Your company account with developer access granted by the administrator.
- The installation's download-page link, normally supplied in the workspace invitation.
- An OpenSSH client on your computer. Check that
sshis available in your terminal. - Access to the coding-provider accounts you intend to use; GitHub access only if choosing a repository.
No enrolment PIN or manually entered developer ID is required for an Integration Server workspace. If developer access is refused, ask the administrator to check your entitlement.
Where it lives
| On your computer | On the Integration Server |
|---|---|
| Downloaded client and its installation configuration | Managed Linux account and persistent home |
| SSH private key and connection entry | Registered public key and managed platform configuration |
| Browser for company and vendor sign-in | Git, GitHub CLI, Node, npm, tmux, Builder CLI, Claude and Codex |
| Codex app when using its remote-project interface | Project files, Agent Kit and coding sessions |
The server provides the workspace configuration and certificate. Keep work under the managed work directory, and leave managed configuration to the administrator. A persistent home survives normal server redeployment; follow your organization's backup policy for recovery.
How to set
- Download and extract the client. Open your installation's download page, such as
https://platform.example/integrator/download, and select your operating system. Keep the suppliedaifabrix.jsonbeside the executable; it identifies the installation. - Run the downloaded executable. On Windows, double-click
aifabrix.exe. On macOS or Linux, run the extracted executable from its folder. Follow the company sign-in address and code, approve in your browser, and return to the client. - Choose your coding clients and project. Select Codex, Claude, or both. Enter a GitHub organization/repository address, or skip GitHub for a local project on the server. This guided client flow does not create repositories, commit or push to GitHub.
- Complete vendor sign-ins. GitHub and Codex use the displayed browser flow. For Claude, open the displayed address, sign in, and paste the returned code into the client: Ctrl+V on Windows, Cmd+V on macOS, or Ctrl+Shift+V on Linux. On Windows, use Ctrl+V rather than right-click paste.
- Trust the named project folder. Review its exact path. Folder trust lets the coding client load project instructions and settings; it does not approve all tools. Complete any first-use screens and exit that first-use session when prompted.
- Open the prepared project. Claude remains in the named remote session: use Remote Control or the printed SSH attach command. For Codex, open your local Codex app, add a connection to the printed host and select the printed project. “Remote project ready” means you still need to open it there.
The client registers your public SSH key, pins the server host key and creates the SSH connection entry. Your private key remains on your computer. Valid vendor sign-ins are reused when you return.
Defaults and examples
Run the downloaded client again to resume unfinished setup or choose a previously prepared project. For a terminal connection from your computer:
ssh aifabrix
Use the alias printed by the client if you chose another installation name. On the remote workspace, start with:
af help
af auth status
For basic SSH work, Git identity, sessions and recovery, continue to Prepare a managed coding workspace. An older workspace toolchain may open a terminal and ask you to run af onboarding there.
Validate
Confirm the client finishes without an unresolved “Not finished” message, the intended project opens, and remote af auth status identifies the expected platform. Company authentication, vendor authentication and project readiness are separate checks.
Before committing, check your Git name and email on the workspace. Then continue with Quickstart: new external system in the intended development environment.
Common mistakes
| Symptom | Next action |
|---|---|
| Wrong installation or missing configuration | Use the correct download and keep its configuration beside the executable |
| Browser does not open | Open the printed address and use the displayed code |
| Setup stopped part-way | Run the downloaded client again; it rechecks missing steps |
| SSH public-key refusal | Ask the administrator to check enrolment and developer access |
| Codex project does not open automatically | Add the printed remote connection in your own Codex app |
Limits
The Integration Server supplies Claude and Codex. Cursor does not need a runtime on that server: connect with SSH and open the project in the Cursor desktop app on your computer. Developers have neither root access nor Docker inside the workspace; ask the administrator for system-wide tooling changes. Workspace readiness does not certify an integration or grant permission to publish to production.