Halyard

Turn local projects into finished work with the model that fits each step.

Halyard is Token Harbor's Windows desktop agent for working directly with files and projects on your computer. Give it a goal and Halyard can inspect your workspace, make permitted edits, run commands, and validate the result.

Choose a model from the Token Harbor catalog, or enable TH Orchestra to select a suitable model as the work progresses — all through one Token Harbor account.

Halyard accesses files and runs commands locally. When model reasoning is needed, relevant task context is sent through Token Harbor. Halyard is currently available in Early Access for Windows 10 and 11.

What Halyard does

Halyard gives a model the tools it needs to complete practical work inside a local project:

• Read files in a selected workspace.
• Create and edit files when workspace writing is allowed.
• Run local commands needed to inspect, build, test, or validate a project.
• Use a model selected from the Token Harbor catalog.
• Use TH Orchestra to choose a suitable model as the task progresses.
• Keep work organized into local workspaces and sessions.
• Access available models through Token Harbor without configuring a separate provider key for every model.

Halyard is useful for code changes, repository exploration, documentation, research projects, structured file editing, and other tasks that benefit from both model reasoning and local tools.

Requirements

• Windows 10 or Windows 11.
• A Token Harbor account.
• Internet access for signing in and sending model requests.
• Permission to install and run an Early Access application on your computer.

The current Windows download is approximately 80 MB.

Download and first launch

1. Open the Halyard download page.
2. Select Download for Windows.
3. Run the downloaded installer.
4. Open Halyard after installation.
5. Sign in with your Token Harbor account when prompted.

Windows security warning

The Early Access build is not yet code-signed. Windows may display a warning the first time you open it.

To continue:

1. Select More info.
2. Confirm that the application is Halyard from Token Harbor.
3. Select Run anyway.

Only install Halyard from the official Token Harbor website. If the file came from another source, do not bypass the warning.

How Halyard runs

Halyard runs on your computer and opens its interface in your browser through a local address on port 3080. The hostname or complete URL may vary by installation or launch environment; use the address opened by Halyard or shown when the local app starts.

Closing the browser tab does not necessarily stop Halyard. The desktop process can continue running in the Windows system tray.

From the Halyard tray menu, you can:

• Open Halyard.
• Stop the local app.
• Check for or install an update.
• Uninstall Halyard.
• Choose whether Halyard starts when you sign in to Windows.
• Open logs for troubleshooting.
• Quit Halyard completely.

Add a workspace

A workspace is the local folder Halyard is allowed to work with. Add the project or folder before starting a task.

1. Open Halyard.
2. In the Workspaces section, select the add-workspace control.
3. Choose the local folder you want to use.
4. Confirm that the correct workspace appears above the composer.

Choose the smallest folder that contains everything needed for the task. Avoid selecting a broad directory that contains unrelated projects, credentials, backups, or personal files.

You can add more than one workspace and switch between them from the sidebar. Sessions remain organized under their workspace.

Start a session

1. Select a workspace.
2. Select New Session.
3. Choose a model, or enable TH Orchestra.
4. Review the active workspace access mode in the composer.
5. Describe the result you want Halyard to produce.
6. Review the proposed work and any actions that require your confirmation.

A useful first task is:

Summarize this repository, identify its main folders, and explain how to run its tests. Do not change any files.

This lets you confirm that Halyard can see the intended workspace before allowing it to make changes.

Write effective tasks

Halyard works best when a task includes the outcome, scope, and validation method.

For example:

Add input validation to the signup form in this workspace. Preserve the existing design, add tests for invalid email addresses, and run the relevant test suite when finished.

Useful details to include:

• The file, folder, or feature to work on.
• What should change and what must stay unchanged.
• Any framework, style, or project conventions to follow.
• Whether Halyard may edit files or should only inspect them.
• Which tests, commands, or checks should be run before completion.

For a larger task, ask Halyard to inspect the project and explain its plan before making changes.

Select a model

Use the model picker in the composer to select an available Token Harbor model. Model availability depends on the current Token Harbor catalog and the access available to your account or Pass.

Selecting a model gives you direct control over which model handles the session. This is useful when you already know which model you want for coding, research, writing, or reasoning.

If the composer says This model is unavailable, open the model picker and select another model that is currently available to your account.

Use TH Orchestra

Enable Orchestra when you want Token Harbor to choose the model instead of selecting one manually.

Halyard starts with th-orchestra, which can select a model for each turn based on the task. This is useful for work that changes across a session—for example, repository analysis followed by implementation, testing, and documentation.

Use manual model selection when model consistency matters more than automatic routing. Use Orchestra when you want the system to adapt the model choice as the work changes.

Workspace access and permissions

Halyard can read files, edit them, and run commands on your computer. These actions are real local operations, so the workspace and permission settings should match the task.

Before sending a task:

• Confirm that the correct workspace is selected.
• Review the access mode shown in the composer.
• Use read-only or restricted access when you only need analysis.
• Enable workspace writing only when the task requires file changes.
• Review sensitive or destructive operations before approving them.

Recommended precautions:

• Commit or back up important work before a large change.
• Do not place secrets in prompts.
• Keep .env files, private keys, credentials, and personal data outside the selected workspace when possible.
• Ask Halyard to show a plan before performing broad refactors.
• Review the resulting diff and test output before accepting a change.
• Do not approve a command you do not understand.

Files, commands, and model calls

The Halyard application, workspace access, and command execution run on your machine. Halyard sends model requests through Token Harbor when a task needs model reasoning.

Relevant file content, command output, and task context may be included in those model requests when needed to complete the task. Selecting a local workspace does not mean that every file is uploaded automatically; however, content used in a model request leaves the machine as part of that request.

Only select workspaces whose content you are permitted to process with the chosen model route. For current data-handling terms, see Token Harbor's Privacy Policy and the policy applicable to the selected model route.

Sessions and workspaces

Use separate sessions for separate outcomes. A focused session is easier to review and less likely to carry irrelevant context into later work.

Recommended organization:

• One workspace per repository or project folder.
• One session per feature, investigation, document, or fix.
• Start a new session after switching to an unrelated task.
• Give each task enough context to be understood without relying on an older session.

The sidebar lets you create new sessions, return to existing sessions, search workspaces, and switch between projects.

Token Harbor access and billing

Halyard uses your Token Harbor access for model calls. Available models and usage depend on your account, Free access, wallet balance, and active Pass.

• A Pass may unlock additional models and included usage.
• Free-model access remains subject to its own allowance and data settings.
• Paid usage follows the pricing or included-usage rules shown in Token Harbor.
• TH Orchestra may route different turns to different eligible models.

Check the Token Harbor dashboard for your current usage, balance, Pass status, and limits.

Common tasks

Understand a project

Map the structure of this repository, identify the main entry points, and explain how data moves through the application. Do not edit anything.

Implement a focused change

Add a loading state to the subscription checkout button. Follow the existing component patterns, update the relevant tests, and run only the affected test suite.

Diagnose a problem

Investigate why the development server fails to start. Inspect the configuration and logs, explain the root cause, and do not change files until I approve the proposed fix.

Improve documentation

Review the setup instructions in this workspace. Update the README so a new developer can install dependencies, configure the environment, and run the project locally.

Validate a repository

Inspect the available scripts, run the safest relevant lint and test commands, and summarize any failures with their likely causes.

Troubleshooting

The model is unavailable

Open the model picker and select a model available to your Token Harbor account. If you expected access to the model, check your Pass and account status in the Token Harbor dashboard.

The composer is unavailable

Confirm that a workspace has been added and selected. Then select an available model or enable Orchestra.

Halyard cannot edit a file

Confirm that the file is inside the selected workspace and that the active access mode permits workspace writing. Also check the file's Windows permissions and whether another application has locked it.

A command fails

Read the command output first. The project may require dependencies, environment variables, a specific runtime, or permission that is not currently available. Ask Halyard to explain the failure before retrying with broader permissions.

The browser interface does not open

Find Halyard in the Windows system tray and select Open Halyard. If the local app is stopped, start or reopen Halyard. The interface uses local port 3080, but the hostname or complete URL may vary; use the address provided by the running app.

Halyard appears offline

Check your internet connection and Token Harbor sign-in status. Local files may still be present, but model calls require connectivity to Token Harbor.

Windows shows a warning

Confirm that the installer came from the official Token Harbor website. For the unsigned Early Access build, select More info → Run anyway only after verifying the source.

You need diagnostic information

Open the Halyard system-tray menu and select Open Logs. Include the relevant error and app version when contacting support, but remove secrets or sensitive project content first.

An update is available

Use Update from the Halyard system-tray menu. Because Halyard is in Early Access, updates may include behavior or compatibility changes.

Early Access notes

Halyard is an Early Access product. Features, supported models, permission controls, interface details, and local runtime behavior may change as the product develops.

Before using Halyard for production or sensitive work:

• Keep an independent backup or version-control history.
• Review every material change.
• Test the result in an isolated or development environment.
• Report unexpected behavior with the app version and relevant logs.

For help, contact support@tokenharbor.ai or use the Token Harbor community support channel.