Configure an Agent Harness and Model Provider

Set up the agent runtime for a workspace. All projects in it use the same settings. This guide configures workspace defaults and verifies them with a manual agent run.

Before you begin

You need:

• The provider's API key. The form asks for any other provider values.
• A project that can sync workflow files.
• An online runner with the ubuntu-latest label.

Configure the agent runtime

Use the Model Providers reference to compare the choices. It lists provider IDs, default models, required credentials, and harness support.

Check the workspace defaults

Stay in Settings → Agents and check the current values:

• Under Harnesses, the star marks the default harness.
• Under Configured providers, the star marks the default provider.
• Open the default provider's menu. Select Change default model to review its model. For a custom provider, select Edit instead.

Use the same controls to correct a value that is not the one you want.

Run the workspace defaults

Create .shipfox/workflows/check-agent-defaults.yml. This complete workflow omits harness, provider, and model. The agent step resolves all three from the workspace settings you checked above.

# yaml-language-server: $schema=https://www.shipfox.io/docs/workflow.schema.json
name: Check agent defaults
runner: ubuntu-latest

triggers:
  manual:
    source: manual
    event: fire

jobs:
  check:
    steps:
      - key: summarize
        prompt: Read this repository and summarize its purpose in one sentence.

Commit and push the file to the project's default branch. Open the project's Workflows tab. Wait for Check agent defaults to sync. Select Run, then open the new run.

Verify the agent run

The step declares no overrides. Shipfox therefore uses the starred harness and provider in Settings → Agents, plus the provider's default model.

Open the check job and its agent step. A completed step with a one-sentence response confirms that the defaults resolved and the saved credentials worked.

If the agent step fails

• If the workflow does not sync, use Troubleshoot workflow sync.
• If the run shows a provider, credential, or model warning, follow the action in that warning. Compare the selection with the Model Providers reference. Run the workflow again after the fix.
• For another runtime failure, open the agent step and use Inspect logs to review its messages and tool results.