← Back to modules
Xebia Axis · Sandbox

How to use the Axis CLI

A browser terminal for the readiness → migration pipeline. Nothing to install — just sign in and run.

Before you start: have your Anthropic API key (sk-ant-…) ready. You paste it into the terminal each session; it is never stored and disappears when the session ends. Each launch also gets its own dated SharePoint folder holding that session's inputs and its output.zip.

Your SharePoint folder

Before you can upload or download, a platform admin sets up your personal folder. They create a folder named after your email address (for example axis-sandbox/jane.doe@xebia.com) and share edit access to that folder — and only that folder with you.

You'll receive an email invitation. Open it to reach the folder you'll use to upload inputs and download outputs. You can only see your own folder, not anyone else's.

Folder-access email

1Sign in

Open the portal and click Sign In with your corporate account.

Sign-in page

2Choose a module

Pick a CLI module — Readiness, Cloud Infrastructure, or Migration. A terminal opens in a new tab. (Axis UI opens the separate Axis app instead.)

Module cards

3Upload input and sync it in

The terminal shows your session folder (e.g. axis-sandbox/<your-email>/2026-09-08_143205). Upload your code as .zip files to that folder in SharePoint, then run:

sync

This pulls every .zip into /work/input/. Uploaded more later? Run sync again.

Terminal after sync

4Set your key

export ANTHROPIC_API_KEY=sk-ant-…your-key…
Setting the API key

5Run the pipeline

Analyse with the readiness repo, then convert with the migration repo (tell it to use the readiness results):

cd /opt/adf-xlens-skills claude # ask it to run over your input in /work/input cd /opt/adf-xport-skills claude # ask it to convert, referring to the readiness results

When you want to keep results, ask Claude to write them to /work/output/ — no need to move files by hand.

Running the pipeline

6Save your results

Nothing is saved automatically. When you're happy, run:

publish

This uploads /work/output as output.zip into the same session folder — alongside your inputs.

Publishing output

✓Good to know

Sessions last up to 2 hours and end after 5 minutes idle (a banner warns you first). Closing the tab ends the session and clears its files — publish first if you want to keep anything. One session at a time per person; launching again starts a fresh one.