Status
35 capabilities are shipped and 2 are planned, as of 2026-10-22, in workspace version 0.26.0. Shipped means implemented on main and held by a named test in the repository; harness-docs generates this page and website/data/status.json from one list and fails when a test it names is gone. Planned means recorded on the repository's plan and not built. What a green test does not show, and what Harness does not do, is on Limitations.
Provider wires
More columns: swipe horizontally, or focus the table and use the arrow keys.
Agent loop
More columns: swipe horizontally, or focus the table and use the arrow keys.
Tools and approvals
More columns: swipe horizontally, or focus the table and use the arrow keys.
Command line
| Capability | Status | What it means | Held by |
|---|---|---|---|
| Toolset description | ● shipped | The tools command describes the toolset without an endpoint. | crates/harness-cli/tests/end_to_end.rs::the_tools_subcommand_describes_the_toolset_without_an_endpoint |
| Profiles | ● shipped | Every profile that contributed to a run is in its record with its own digest. | crates/harness-cli/src/profile.rs::every_profile_that_contributed_is_in_the_record_with_its_own_digest |
| Default write scope | ● shipped | The default write scope denies the repository's own Git directory. | crates/harness-cli/src/profile.rs::the_default_write_scope_denies_git |
| Declared context files | ● shipped | A declared context file that is absent refuses the run before any session is filed. | crates/harness-cli/tests/context.rs::a_declared_context_file_that_is_absent_refuses_the_run_before_any_session |
More columns: swipe horizontally, or focus the table and use the arrow keys.
Sessions and output
| Capability | Status | What it means | Held by |
|---|---|---|---|
| Resume | ● shipped | A run files its conversation, and a later run resumes it. | crates/harness-cli/tests/end_to_end.rs::a_run_files_its_conversation_and_a_later_one_resumes_it |
| Sessions stay outside the workspace | ● shipped | A session directory inside the workspace is refused before it is created. | crates/harness-cli/src/transcript.rs::a_session_directory_inside_the_workspace_is_refused_before_creation |
| JSON events | ● shipped | JSON mode emits one event per line. | crates/harness-cli/tests/end_to_end.rs::json_mode_emits_one_event_per_line |
More columns: swipe horizontally, or focus the table and use the arrow keys.
Delegation, skills, memories and hooks
More columns: swipe horizontally, or focus the table and use the arrow keys.
Bridge mode
| Capability | Status | What it means | Held by |
|---|---|---|---|
| Tool calls round trip | ● shipped | A tool call round trips back to the client that registered the tool. | crates/harness-cli/tests/bridge_mode.rs::a_tool_call_round_trips_back_to_the_client |
| Pinned method inventory | ● shipped | The client methods served and refused match the pinned profile manifest. | crates/harness-app-server/tests/contract.rs::the_served_and_refused_client_methods_match_the_manifest |
| Driven by a real external client | ○ planned | A real external client drives bridge mode end to end, beyond the contract tests. |
More columns: swipe horizontally, or focus the table and use the arrow keys.
Specification
| Capability | Status | What it means | Held by |
|---|---|---|---|
| The loop in the executable specification | ○ planned | The agent loop's turn, tool and budget behaviour is modelled in the executable specification and run by its conformance suite. |
More columns: swipe horizontally, or focus the table and use the arrow keys.