All documentation

Clients

A client is a coding agent that Besydr works with. Besydr can only do what a client lets an extension do, so the features differ by client. Where a client lacks a feature, Besydr turns that feature off for it. It does not imitate the feature in another way.

Octomind talks to Besydr through a plugin protocol that was built together with these features. The four other clients are connected through their hooks or extensions (see Install), and the gaps below apply to them.

Features by client

Feature Claude Code Codex OpenCode pi
Lessons added to the agent's context with each request Yes Yes Yes, in the system prompt Yes, as a hidden message
Standing rules and checklist repeated, and sent again after a compaction Yes Yes Yes Yes
Learning from sessions Yes Yes Yes Yes
Completion check (agent sent back to work) Yes Yes Yes, except one-shot opencode run Yes
Tool admission (a call can be denied) Yes Yes Yes Yes
Notes after a tool call (loop and no-progress notes) Yes Yes Yes Yes
Notices shown to you Yes Yes Yes, as a toast Yes
Condensing of large tool output Bash only No Yes, every tool Yes, except failed calls
Blocking a prompt Yes Yes No Yes
Note at the end of a turn No No No Yes
The agent's tool list sent to Besydr No No No Yes
Events when a subagent finishes Yes Yes No No
Plan shown and applied No No No No
Status view and /learning command No No No No

"Yes" means the client carries the answer and the adapter sends it. It does not mean the mechanic is switched on; see Mechanics for the settings.

Why a feature is missing

Completion check:

  • OpenCode: a one-shot opencode run ends as soon as the session is idle, before the plugin's new prompt can start a turn, so the agent is not sent back there. With opencode serve and opencode run --attach the agent went on after Besydr asked (OpenCode 1.19.5). The terminal UI was not checked. Condensing:
  • Claude Code: it accepts a replaced tool output only in the output format of that tool, and only the format of Bash is documented.
  • Codex: its hooks have no field that replaces a tool's output.
  • pi: a failed tool call cannot be replaced.

Blocking a prompt:

  • OpenCode: no plugin hook is documented that stops a prompt.

Notes at the end of a turn:

  • Claude Code and Codex: the Stop hook can only continue the turn or not; it has no place for text beside that.
  • OpenCode: the event at the end of a turn has no place for a note. It also has no place for a note before a tool call.

Context before a tool call:

  • Codex: its documentation lists text next to a tool call for PreToolUse, but a field Codex refuses makes the whole hook count as failed and would lose a denial, so the adapter leaves it out until it is checked against the Codex version in use. Context after a tool call works.

Tool list:

  • Claude Code and Codex: hook input does not carry the tools with their descriptions.
  • OpenCode: a plugin is not given the tools at session start.

Subagents:

  • Claude Code and Codex: hooks report only when a subagent stops, not when it starts. A subagent's tool calls appear under the session that started it.
  • OpenCode: a subagent runs as a session of its own, and the plugin reports it as one.
  • pi has no subagents.

Plan:

  • None of the four clients gives a hook or extension a way to read or change the agent's plan. Besydr keeps its own plan for these sessions.

Status view and /learning:

  • None of the four clients lets an extension register a slash command or show rows in its own status view, so these exist in octomind only. For lessons with the other clients, see Learning.

Ending a turn right after a tool call:

  • OpenCode and pi: no result field ends the turn after a tool. Codex documents continue: false as replacing the tool result, not as ending the turn. Only Claude Code supports it. No mechanic needs it in this release.

Other limits

  • Codex runs a hook only after you have reviewed and trusted it in /hooks. Until then Codex runs as if Besydr were not installed.
  • Codex's shell tool is named Bash in hook input; the adapter treats only that name as a shell. With Codex 0.167.0 a command run through the tool exec_command arrived as Bash. Codex has also been seen to run commands through a custom tool named exec. Whether hooks report that tool as Bash is not documented. If they report exec, Besydr sees the call but does not treat it as a shell command.
  • Codex does not always run a hook after a patch that a model sends through the shell (apply_patch <<'EOF' ...). When it runs none, the adapter reports the patch from Codex's session file at the session's next hook, so Besydr learns about that change one hook later than about other tool calls.
  • Codex hooks are not a complete enforcement boundary, according to Codex's own documentation, so a denied call in Codex is a strong default and not a guarantee.
  • Claude Code and Codex write session files that they document as internal or unstable. Besydr reads what the files contain today and skips what it does not know. A format change means Besydr sees fewer messages. It does not make a hook fail.
  • In runs with Claude Code 2.1.282, Codex 0.167.0, OpenCode 1.19.5 and pi 1.5.2, no client gave its version to a hook or an extension, so Besydr records the version as unknown. The OpenCode plugin targets the 1.x plugin interface and has not been checked against OpenCode 2.
  • OpenCode and pi do not report which MCP server a tool belongs to, so the server is empty.
  • Every client: when Besydr cannot be reached or does not answer in time, the client goes on as if Besydr were not installed.