Skip to content

v0.7.0 — ledger-based conclusion, review by the other side

Choose a tag to compare

@thejohnd0e thejohnd0e released this 07 Nov 00:47
· 6 commits to master since this release

The joint conclusion is now built on the claim ledger, and the other side can check it. Installation and tests also work better on macOS and Linux.

A conclusion that follows the ledger

A reviewer found that a claim from the very last reply had been listed as a disagreement, although nobody had a turn left to answer it. Open claims now have two distinct states:

  • skipped by the opponent: the opponent had a turn after it and did not answer. This is a disagreement.
  • left open: the debate ended: it came in the last reply. This is not a disagreement.

With a ledger, the conclusion gets the claims grouped by state and has four sections: agreed, disagreed, left open when the debate ended, recommended next steps. It is told to rely on the ledger instead of reconstructing the debate.

Review of the conclusion by the other side

/discuss-settings conclusion=b review=on: after the conclusion, the side that did not write it gets one request to list distortions, such as a point in the wrong section, an agreement that never happened, its own position misstated, or a claim from the last reply shown as a disagreement. If it finds none, it answers "No objections." It does not reopen the debate. The panel shows the review as "Review of the conclusion · by A", and the handoff puts it right after the conclusion.

  • The reviewer gets the same section rules as the writer, so it does not demand a different structure.
  • The review is advisory. If it fails, the run still completes with its conclusion, and the panel and handoff say the review was not received.
  • The conclusion and the review read the whole discussion, so reasoning models think longer there. Both get an output cap of at least 12000 tokens, lowered to a model's advertised limit when known. The start dialog counts this in the ceiling.

Easier to install, works beyond Windows

  • bun run install-agents copies the two agent files into ~/.config/opencode/agents/. It leaves identical files alone and backs up a changed one first. Add --dry-run to only see what it would do.
  • Without options.python, the plugin runs python on Windows and python3 on macOS and Linux.
  • The smoke tests find opencode on PATH (or OPENCODE_BIN) and use the system temp directory.
  • .gitattributes keeps LF line endings on every platform.
  • The runner no longer has a default model pair, and local test-machine details were removed from the docs.

Verified

  • Live runs (DeepSeek Flash vs GPT-6 Luna, 3-round debates):
    • A claim from the last reply is now filed as "left open", not as a disagreement.
    • In one run the review caught a real distortion: a claim accepted only in part was listed as fully agreed. Two of its other objections asked for a different structure, which led to the section-rules fix.
    • After the fixes, a full run completed with 8 of 8 calls, the conclusion matching the ledger and "No objections." ($0.004).
  • Not yet seen live: a failed review completing the run, which is covered by tests.
  • Tests: 222 unit tests and 43 Python bridge tests pass; typecheck, build and both smoke tests are OK.

Full changes: v0.6.1...v0.7.0