Skip to main content

Better Harness

Install Better Harness and review project instructions, validation workflows, and recurring friction in agent work.

Better Harness is an engineering review Plugin available in the marketplace. Use it when agents repeatedly overlook project conventions, skip validation, or depend on the same manual steps. Review the evidence before deciding which rules, Skills, or checks to improve. Install the Plugin before first use.

Understand the review scope

What is an Agent Loop? An agent typically cycles through understanding a task, taking action, checking the result, and adjusting its next step. This is the Agent Loop. It needs clear goals, operating boundaries, and evidence that the task is complete. What is an Agent Harness? The Harness is the engineering environment that supports this loop: project context, available tools, permission boundaries, validation methods, and mechanisms for retaining lessons. Loop Engineering focuses on feedback and improvement within each cycle; Harness Engineering connects these supporting mechanisms to the project so later tasks can use them too. Different assets serve different purposes: Rules record project conventions; Skills provide reusable task methods; Hooks run checks or actions at specified events; Plugins package extensions; and Connectors connect external tools and data. Test scripts and delivery checks provide evidence of correctness. Choose assets to address a specific problem rather than adding every type of configuration to every project. Why use Better Harness? One successful task does not establish that a project's workflow is reliable. Repeated reminders about the same convention or repeatedly missed checks point to gaps worth examining. Better Harness helps you use evidence to choose a lasting improvement, such as documenting a convention in a rule or turning a repeated check into a script. Depending on your request and available evidence, a review can examine:
  • Whether agents can find project guidance, execution entry points, and validation commands.
  • Whether existing rules and Skills support ordinary work.
  • Which steps repeatedly need reminders, and which feedback should become a lasting workflow.
Specify the records and scope when requesting analysis of earlier tasks. A project review does not establish that every historical conversation was examined. Explicitly request a report or project initialization when needed.

Install Better Harness

  1. Open Extensions in the left sidebar and select Plugins.
  2. Search for Better Harness and open the Plugin published by Qoder.
  3. Review its description and included Skills, then select Install. Skip installation if it is already installed.
  4. Confirm that Enable in task is on in the details page.
The Plugin includes Skills such as better-harness and init. This guide uses better-harness to review a project; check the Skill name when selecting it. See Plugins for management instructions.

Start a review

  1. Start a new task in the workspace you want to review.
  2. Type /better-harness and select the better-harness suggestion of type Skill. Press Enter or Tab to add it.
  3. Confirm that the better-harness item appears in the input, then describe the target, problem, and expected output.
  4. Send the message and follow the execution and reply in the task.
Start with analysis and recommendations before requesting changes, for example:
Review why this project repeatedly misses link validation before release.
Analyze only this project. Explain the evidence and recommendations in chat without changing files.
The Try button on the Plugin details page adds Better Harness to a new task. From there, follow the steps above to type /better-harness, select the review Skill, and describe your request. Try adds the Plugin; the slash suggestion selects a specific Skill.

Review findings and make improvements

Check the tool execution status before reading the reply. For each finding, confirm the evidence, affected scope, proposed change, and verification method. Keep unsupported conclusions pending. If you requested a report, open the report link returned in the task. Use the actual execution result to confirm that the report was generated. Choose one recommendation with a clear acceptance criterion, then start a task to implement it. For example, document a missing project convention or turn repeated validation into a script. Run the relevant checks and verify the improvement in later tasks. Avoid making one-off preferences or transient failures permanent rules.

Troubleshoot the command

  • No matching suggestion: check that Better Harness is installed under Extensions → Plugins and enabled for tasks.
  • Wrong item selected: type /better-harness again and select Skill better-harness, rather than init or the Plugin item.
  • Skill not found or a failed tool call: check the Plugin state, try the refresh button on its details page, and retry in a new task. If it still fails, keep the error details and report them through the client's feedback entry.
A visible suggestion or an ordinary agent reply does not prove that Better Harness ran successfully. Confirm that the relevant Skill call succeeded before using its findings.