Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The Frontier Tuning CLI (frontier-tuning, or the shorter alias ftune) is the command-line tool for building and operating tuning environments. Use it to provision a tuning environment, define skills and evaluation criteria, and upload samples. You can also run queries and start evaluation and fine-tuning jobs. Every command uses one Microsoft 365 sign-in.
The Frontier Tuning plugin for GitHub Copilot and other coding agents also use the CLI to perform operations against the service.
Important
Frontier Tuning is in public preview. Features, limits, and availability can change, and some capabilities are enabled per tenant or per environment.
Prerequisites
- Access to Frontier Tuning. During public preview, your admin must include you in the tenant's Copilot Frontier audience, and you need a Microsoft 365 Copilot license. For admin steps, see Enable Frontier Tuning.
- A supported operating system. Windows, macOS, Linux, or Windows Subsystem for Linux (WSL).
- Python 3.10 or later. The installers set up Python for you when needed. Automatic setup on Windows requires winget.
- An interactive terminal for Microsoft 365 sign-in.
- Package-feed access, if your organization routes Python package installation through an internal feed. Configure access before you install.
You don't need administrator rights to install the CLI.
Install the CLI
Choose the installer for your operating system.
To install the CLI on Windows, follow these steps:
Open PowerShell and install the CLI:
irm https://aka.ms/ft-cli/v1/ps1 | iexWait for the installation to finish. The installer checks the downloaded package's checksum.
Open a new terminal so that the updated
PATHtakes effect, or use the direct command path that the installer prints.
The Windows installer creates a private, per-user Python environment under %LOCALAPPDATA%\frontier-tuning\v1\env and adds only the CLI commands to your user PATH. It doesn't change your existing Python packages. If a compatible Python isn't available, it can install Python for the current user through winget, without administrator access.
Note
On Windows on Arm devices, use x64 Python. Native Arm64 Python isn't supported by the Windows installer.
Confirm that the CLI is installed by checking its version:
frontier-tuning --version
Sign in and confirm access
Use your organization's Microsoft 365 account to sign in and check access:
In an interactive terminal, sign in with your organization's Microsoft 365 account:
frontier-tuning auth loginThe first sign-in for each installed CLI version shows the Frontier Tuning preview notice. It asks you to acknowledge the Microsoft 365 supplementary terms before sign-in starts.
Confirm that your account can access Frontier Tuning:
frontier-tuning auth checkIf access is denied, follow the guidance that the check command displays. An administrator might need to grant consent or access.
Other sign-in commands:
| Command | Use it to |
|---|---|
frontier-tuning auth login --interactive |
Sign in again or choose a different account. |
frontier-tuning auth whoami |
Show the signed-in identity that every command uses. |
frontier-tuning auth refresh |
Refresh your authentication. |
frontier-tuning auth logout |
Sign out and clear saved CLI credentials. |
frontier-tuning auth probe |
Verify sign-in and access to the selected tuning environment. |
Tip
Sign in from a terminal before you use the CLI from an agent host such as the GitHub Copilot app. Agent hosts run commands without an interactive terminal, so they can reuse an existing sign-in but can't show a sign-in prompt.
For unattended automation, you can accept the preview terms with --accept-preview-terms or by setting FRONTIER_TUNING_ACCEPT_PREVIEW_TERMS=true. Accepting the terms doesn't provide credentials, grant consent, or bypass Microsoft Entra Conditional Access. Confirm that your organization's sign-in policy supports the scenario. Managed-device policies might block device-code sign-in.
Select the tuning environment that commands use
When you create a tuning environment with frontier-tuning environments create, the CLI saves its ID as your default automatically. To check which tuning environment is selected, run:
frontier-tuning config show
To run a command against a different tuning environment, pass its ID with -e (or --env-id):
frontier-tuning -e <env-id> skills list
Add -o json to any command for machine-readable output, and use --help on any command to see its options.
Keep the CLI up to date
Automatic updates are on by default. The CLI checks for a newer v1 release at most every two hours and installs it after the next command finishes.
| Task | Command |
|---|---|
| Check whether a newer version exists, without installing it | frontier-tuning update --check |
| Update now | frontier-tuning update |
| Turn off automatic updates | frontier-tuning config set auto_update false, or set FRONTIER_TUNING_AUTO_UPDATE=false |
On Windows, an update's exit code 0 means that the update was scheduled, not that it finished. Read the status.json file whose path the command prints, and wait for "state": "succeeded" before you run the CLI again. On macOS and Linux, updates complete before the command returns.
Note
Starting with CLI version 1.0.21, only the public connection setting is supported. If your configuration, a profile, or the FRONTIER_TUNING_TRANSPORT environment variable still uses legacy or workiq, commands stop and explain how to migrate. Run frontier-tuning config set transport public, update any remaining profile or environment variable, and then run frontier-tuning auth login and frontier-tuning auth check.
Use the CLI on a managed network
- Internal package feed. Both installers honor pip configuration and the
FRONTIER_TUNING_PIP_INDEX_URLsetting, so you can route installation through an approved internal feed. Feed authentication failures stop the installation rather than opening a hidden credential prompt. - Corporate proxy. The CLI trusts the certificates in your operating system's certificate store, including your proxy's certificates, and uses
HTTPS_PROXY,HTTP_PROXY, or the operating system's proxy settings. To verify against the CLI's bundled certificate list instead, setFRONTIER_TUNING_SYSTEM_TRUST=0. - Custom request headers. Use the
--headeroption only when your service administrator supplies headers to use.
Use the CLI with a coding agent
Microsoft publishes guidance for coding agents that can read Markdown and run the CLI. It includes a SKILL.md entry point plus playbooks for onboarding, creation, preparation, evaluation, and tuning. The guidance doesn't install tools or grant permissions. It tells the agent to ask before changing resources or starting paid work. For a packaged experience in GitHub Copilot, see Use the Frontier Tuning plugin for GitHub Copilot.
Troubleshoot installation and sign-in
| Problem | What to do |
|---|---|
| The command isn't found after installation. | Open a new terminal to pick up the updated PATH, or use the direct command path that the installer printed. |
| Installation fails with a package-feed access error. | Configure access to your package feed, and then retry. On Windows, a dependency-resolution failure leaves an existing CLI installation in place. |
Windows reports WinError 32 (a locked executable). |
Close any running Frontier Tuning CLI processes, and then retry the installer. |
auth check reports that access is denied. |
Follow the displayed guidance. An admin might need to grant consent, include you in the Copilot Frontier audience, or assign a license. |
| You need to use a different account. | Run frontier-tuning auth login --interactive in a terminal. On Windows, the account picker might appear behind the terminal window. |
When you contact support, never include access tokens or credential-cache files. For CLI commands and options, see the Frontier Tuning CLI quick reference.