# AI use cases for Agnes Harness (AgnesAI-Labs/agnes-harness)

Repo: [AgnesAI-Labs/agnes-harness](https://github.com/AgnesAI-Labs/agnes-harness) | Use cases: 5 | Page: https://dedupedai.com/use-cases/agnesai-labs-agnes-harness/

Agnes Harness is a pluggable, developer-preview (pre-alpha) TypeScript agent harness for Forward Deployed Engineering, run from source, that connects models, tools, task state, and business interfaces.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Add a business tool to the agent as a plugin: https://dedupedai.com/use-cases/agnesai-labs-agnes-harness/add-business-tool-plugin/
- Review a codebase with approvals and a visible trace: https://dedupedai.com/use-cases/agnesai-labs-agnes-harness/review-project-with-approvals/
- Continue a Web task from the terminal: https://dedupedai.com/use-cases/agnesai-labs-agnes-harness/hand-off-web-task-to-terminal/
- Run the Mars rescue demo with virtual devices: https://dedupedai.com/use-cases/agnesai-labs-agnes-harness/run-mars-device-demo/
- Package a backend service with its own workbench panel: https://dedupedai.com/use-cases/agnesai-labs-agnes-harness/package-full-stack-plugin-panel/

## How to add a business tool to the agent as a plugin with Agnes Harness

Repo: [AgnesAI-Labs/agnes-harness](https://github.com/AgnesAI-Labs/agnes-harness) | Difficulty: Intermediate | Time: 1 hour | Basis: From the README

Register a customer-specific tool as a backend plugin so the agent can call it.

**Who it is for:** A solutions engineer whose customer needs the agent to query an internal order or knowledge system.

**The problem:** Writing customer systems directly into the agent means forking it for every deployment.

**The outcome:** A backend plugin registers a tool the agent can call, and each call keeps its inputs and structured output.

### Steps

1. Clone the Agnes Harness repository and open its root directory.
2. Run `pnpm install --frozen-lockfile`.
3. Run `pnpm --filter @agnes/cli build:local`.
4. Read the backend plugin guide at docs/develop/backend.md and start from the demo_text_stats example.
5. Run `node packages/cli/dist/local/agnes.mjs serve`, open the printed loopback URL, and call your tool in a task.

### Prompt to paste into your agent

```text
Work in the agnes-harness repository at <repo path>. Follow docs/develop/backend.md to add a backend plugin that exposes a tool named <tool name> for <business system>. Confirm the tool appears in a task and returns structured output. Report the files you changed.
```

### Caveat

AGH is a pre-alpha developer preview, and ordinary backend plugins run as trusted in-process code, so review plugin code before enabling it.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/agnesai-labs-agnes-harness/add-business-tool-plugin/

## How to review a codebase with approvals and a visible trace with Agnes Harness

Repo: [AgnesAI-Labs/agnes-harness](https://github.com/AgnesAI-Labs/agnes-harness) | Difficulty: Intermediate | Time: 1 hour | Basis: From the README

Ask the agent to explain a project read-only and check each step in the Trace view.

**Who it is for:** An engineer in a customer environment who needs to show exactly what an AI agent read and changed.

**The problem:** A result alone does not show how it was produced, and customers want to know what the AI changed and who approved it.

**The outcome:** A read-only explanation of a project, with a session record and a Trace timeline of model calls, tools, and approvals.

### Steps

1. Run `pnpm install --frozen-lockfile` and `pnpm --filter @agnes/cli build:local` in the source root.
2. Run `node packages/cli/dist/local/agnes.mjs serve` and open the printed loopback URL.
3. Configure a model, create a task, and confirm the working directory and permissions before running it.
4. Send the request: Read this project and explain the problem it solves and how its main directories are organized. Do not modify files.
5. Open the Trace view and check each model call, tool use, and approval in order.

### Prompt to paste into your agent

```text
In the agnes-harness repository at <repo path>, start AGH with `node packages/cli/dist/local/agnes.mjs serve`, then ask it to explain <target project> without modifying files. Expected output: a summary of the project's purpose and directory layout, plus a Trace of every tool call and approval. Verify that no files changed in the target directory.
```

### Caveat

AGH is a developer preview that you run in your own environment, and its APIs and configuration may change.

Risk, credentials: Configuring a model usually requires an AI provider API key, so store it only in your local AGH configuration and keep it out of shared files.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/agnesai-labs-agnes-harness/review-project-with-approvals/

## How to continue a Web task from the terminal with Agnes Harness

Repo: [AgnesAI-Labs/agnes-harness](https://github.com/AgnesAI-Labs/agnes-harness) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README

Resume a session started in the browser and keep working in the CLI with the same history.

**Who it is for:** An analyst who starts a task in the browser and an engineer who needs to pick it up from a terminal.

**The problem:** Copying context between tools loses history and decisions.

**The outcome:** The terminal session shows the same history, tool records, and results as the Web thread, and new terminal messages appear in the Web thread.

### Steps

1. Run `node packages/cli/dist/local/agnes.mjs serve` and keep it running.
2. In the browser, start a task and note its session.
3. Open a second terminal in the same source directory and use the same AGH_HOME or AGNES_PROFILE values if you set them.
4. Resume the Web session in the terminal with /resume.
5. Run `node packages/cli/dist/local/agnes.mjs -p "Briefly explain what this project does"` and check that it appears in the Web thread.

### Prompt to paste into your agent

```text
Using the agnes-harness repository at <repo path>, start the AGH server, create a task in the Web interface, then resume that session from the CLI with /resume. Expected output: the terminal shows the earlier history and the new message appears in the Web thread. Verify both views show the same session ID.
```

### Caveat

The CLI must use the same backend and configuration as the running Web server, so mismatched AGH_HOME or AGNES_PROFILE values will show a different session.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/agnesai-labs-agnes-harness/hand-off-web-task-to-terminal/

## How to run the Mars rescue demo with virtual devices with Agnes Harness

Repo: [AgnesAI-Labs/agnes-harness](https://github.com/AgnesAI-Labs/agnes-harness) | Difficulty: Advanced | Time: 2 hours | Basis: From the README

Coordinate a simulated hopper, robot, and airlock through MHS without any hardware.

**Who it is for:** A field or lab engineer evaluating whether device integration through MHS fits a site workflow.

**The problem:** Device integration is hard to evaluate without physical hardware on hand.

**The outcome:** The agent sends a simulated hopper to find an astronaut and coordinates the robot and airlock, with camera images and observations returned through MOS.

### Steps

1. Complete the source build with `pnpm install --frozen-lockfile` and `pnpm --filter @agnes/cli build:local`.
2. Confirm the model you select supports images and tool calls.
3. Follow the Mars base guide at docs/guide/mars-world.md to start the virtual devices and the @agnes/mhs plugin.
4. Open Mars World in a browser.
5. Give the agent the rescue task and review the Trace of device calls and MOS observations.

### Prompt to paste into your agent

```text
In the agnes-harness repository at <repo path>, follow docs/guide/mars-world.md to start the eleven virtual devices and the @agnes/mhs plugin. Ask the agent to send the hopper to find the astronaut and coordinate the robot and airlock. Expected output: device state reads, action requests, and returned camera observations in the Trace. Verify that Mars World reflects each action.
```

### Caveat

The repository provides virtual devices only, and passing the mhs-check conformance suite does not certify a device as safe.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/agnesai-labs-agnes-harness/run-mars-device-demo/

## How to package a backend service with its own workbench panel with Agnes Harness

Repo: [AgnesAI-Labs/agnes-harness](https://github.com/AgnesAI-Labs/agnes-harness) | Difficulty: Advanced | Time: 3 hours | Basis: From the README

Build a full-stack plugin that pairs a business service with a role-specific Web panel.

**Who it is for:** A plugin developer packaging a business workflow for a support lead or warehouse operator.

**The problem:** Each role needs its own screen, and the interface should stay tied to the service it uses.

**The outcome:** A full-stack plugin with a panel that reads a backend result and can be installed, enabled, updated, rolled back, and removed.

### Steps

1. Complete the source build with `pnpm install --frozen-lockfile` and `pnpm --filter @agnes/cli build:local`.
2. Read docs/develop/fullstack.md and docs/develop/frontend.md and start from the full-stack example.
3. Add a backend service and a sidebar panel that reads its result through controlled calls.
4. Install the plugin, enable it, and verify the integrity digest and capability hash shown before it runs.
5. Run `node packages/cli/dist/local/agnes.mjs serve`, open the panel, then test an update and a rollback.

### Prompt to paste into your agent

```text
In the agnes-harness repository at <repo path>, follow docs/develop/fullstack.md to build a full-stack plugin that shows <business data> in a sidebar panel for <role>. Expected output: the panel loads and displays the backend result, and an update followed by a rollback restores the earlier version. Verify the installed plugin's version, source, and hashes before enabling it.
```

### Caveat

Plugin interfaces are still evolving in this pre-alpha release, so a plugin built now may need changes after an update.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/agnesai-labs-agnes-harness/package-full-stack-plugin-panel/
