Skip to content

Releases

Version 0.504 - Official CPAN release

Choose a tag to compare

@Getty Getty released this 27 Oct 18:11
0.504 2026-10-27T15:45:56Z
 [Before you upgrade]
 - INCOMPATIBLE: every tool call passes a permission policy, always on (ADR
   0021). In the default mode a run nobody can approve -- a one-shot
   `raider "..."`, --json and the --stream-* flags, a Hall raider, ACP --
   refuses writing files, bash, the network and messages unless a rule
   allows them. See [Permissions] for the remedies.
 - INCOMPATIBLE: bash refuses heavy commands (prove, make test, dzil
   test|build|release, cpanm, docker build, ...) while the host is under
   memory pressure or all heavy slots are taken -- the loadguard gate is on
   by default (ADR 0018). LOADGUARD_THROTTLE=0 turns it off. See [Tools].
 - INCOMPATIBLE: a project with only CLAUDE.md, CLAUDE.local.md or .claude/
   is read in Claude mode (ADR 0019): the CLAUDE.md hierarchy, the Claude
   settings (their permissions and env apply, their hooks run), Claude
   skills and agents -- without --claude. Skills are no longer glued into
   the system prompt in full: the prompt lists them, the model loads one
   with the skill tool. See [Claude Code layout and skills].
 - INCOMPATIBLE: a prompt that starts with /NAME is a slash command, also
   in a one-shot run (ADR 0030): `raider "/foo"` with no command or skill
   foo is "unknown command" with exit 2 instead of a prompt to the model; a
   path such as `/etc/hosts is broken` stays a prompt. In command bodies $N
   counts from 0 as in Claude Code ($0 is the first argument). See [Slash
   commands like Claude Code].
 - INCOMPATIBLE: subagents nest up to three levels by default
   (max_agent_depth 3, was 1; max_agent_depth: 1 restores it), the result
   of an agent call ends with an agentId line and a <usage> block, and a
   one-shot run waits for the background agents it started before it ends
   (ADR 0027). See [Claude Code layout and skills].

 [File tools]
 - read_file asks the engine whether images and PDFs may go back as
   content: supports('tool_result_images') and supports('tool_result_pdf')
   (Langertha 0.504), replacing the guess from the wire name. Two separate
   answers, so a model that takes images but no PDFs (or the reverse) gets
   the one and a refusal for the other. FileTools::build_file_tools_server
   has reads_pdf next to sees_images; neither falls back on the other.
 - INCOMPATIBLE: read_file, write_file and edit_file answer like Claude
   Code's Read, Write and Edit (ADR 0023): "File created successfully at:
   P", "The file P has been updated successfully.", "String to replace not
   found in file.", "Found N matches of the string to replace, but
   replace_all is false. ...", "File does not exist. Note: your current
   working directory is ROOT.", "EISDIR: ...", with Claude Code's error
   flags and <tool_use_error> frame. The old "Wrote N bytes" / "Edited" /
   "Error: not a file" texts are gone.
 - INCOMPATIBLE: read before write. write_file, edit_file and multi_edit
   refuse an existing file that was not read in the run ("File has not been
   read yet. Read it first before writing to it.") or that changed on disk
   since ("File has been modified since read, ..."). New files need no
   read; what the tools wrote counts as read; a read with offset/limit
   counts. The record is per run (begin_run empties it) and holds in every
   layout. The CLAUDE.md / AGENTS.md files in the prompt count as read, so
   they can be edited without a read_file first.
 - INCOMPATIBLE: read_file returns cat -n lines ("N<TAB>line") and takes
   offset (1-based) and limit; at most 2000 lines by default with a note
   where the rest is, lines over 2000 characters cut, files over 256 KB
   need offset/limit. Empty files and an offset behind the end give Claude
   Code's system reminders. Binary files, devices and directories are
   refused with a message. Images (PNG, JPEG, GIF, WebP) and PDFs go back
   as image/document content when the model sees images and its wire
   carries them in a tool result, else a clear refusal; Jupyter notebooks
   come back as their cells with outputs. A read over 25000 tokens (bytes /
   4) is refused as in Claude Code; pages ("1-5", at most 20) reads PDF
   pages as text through pdftotext (poppler, looked up on PATH; a PDF of
   more than 10 pages needs it) (ADR 0023 addendum).
 - New tool multi_edit(path, edits) like Claude Code's MultiEdit: edits
   applied in order on the content in memory, atomic, the failing edit
   named by its number. Edit/Write/MultiEdit rules, acceptEdits and the
   plan-mode refusal cover it as they cover edit_file.
 - INCOMPATIBLE: in the Claude layout the file and search tools are no
   longer confined to the root and the additional directories: a path
   outside them asks (refused with how to allow it when nobody can answer),
   allow rules such as Read(//tmp/**) open it, acceptEdits does not cover
   edits outside, bypassPermissions reaches it, deny rules hold. A symbolic
   link out of the root counts as outside. Every other layout stays
   confined ("Path escapes root"), also in bypassPermissions. FileTools and
   SearchTools share one confinement (Langertha::Raider::PathConfine).

 [Shell tools]
 - INCOMPATIBLE: bash answers like Claude Code's Bash (ADR 0024): on exit 0
   only the output -- stdout and stderr as one stream in the order written
   -- or "(Bash completed with no output)"; otherwise an error result "Exit
   code N" followed by the output. The "Exit code: 0" line and the ===
   STDOUT === / === STDERR === blocks are gone, and so is MCP-Run's
   `compress` argument. Output over 30000 characters keeps its start and
   its end around "... [N characters truncated] ...".
 - INCOMPATIBLE: a command still running after its timeout (seconds,
   default 120, at most 600) is no longer killed: it is moved to the
   background with an ID, as in Claude Code.
 - run_in_background: true starts a command in the background and answers
   at once with its ID (bash_1, bash_2, ...). New tools bash_output
   (bash_id, filter, block, timeout: new output, status
   running/completed/killed, exit code) and kill_shell (shell_id: SIGTERM
   to the process group, SIGKILL after 2 s). Background shells are
   supervised by the application's event loop, live across the runs of a
   session, survive a cancelled turn and are stopped when raider ends.
   bash_output is a read tool, kill_shell has no effect class; both run in
   every permission mode. The loadguard gate and allowed_commands are asked
   before a background command starts, too.
 - bash runs through Langertha::Raider::BashTools instead of
   MCP::Run::Bash; the MCP::Run::Bash requirement is dropped. A
   working_directory is entered with chdir: with MCP-Run's "cd DIR &&
   COMMAND", a command such as `x & y` ran y in raider's own directory.

 [Task tools, plan mode and Claude Code tool names]
 - INCOMPATIBLE: the task list is kept with task_create, task_update,
   task_list and task_get, shaped after Claude Code's TaskCreate,
   TaskUpdate, TaskList and TaskGet (ADR 0025): one task per call, ids "1",
   "2", ..., statuses pending/in_progress/completed/deleted, owner,
   metadata, blocks/blockedBy, and Claude Code's answers ("Task #1 created
   successfully: ...", "Updated task #1 status", "Task not found"). They
   replace todo_write in the default tool set, as in Claude Code;
   RAIDER_ENABLE_TASKS=0 mounts todo_write instead. The task list lasts for
   the conversation (todo_write's stays run state); /clear empties it; both
   report it as todo.updated.
 - New tool enter_plan_mode (Claude Code's EnterPlanMode): switches the
   session to plan mode and answers Claude Code's instructions. The
   permission gate asks the person first in default, acceptEdits and auto
   mode ("for this session" adds the rule EnterPlanMode); it runs without a
   question in bypassPermissions and is refused when nobody can agree.
 - INCOMPATIBLE: MultiEdit now means multi_edit, not edit_file, in rules,
   agent files and hook matchers; a hook gets it as MultiEdit with an
   absolute file_path. TaskStop, KillShell and KillBash mean kill_shell
   (task_id <-> shell_id); TaskOutput and BashOutput mean bash_output
   (task_id <-> bash_id, timeout ms <-> s, TaskOutput's default block true
   written down); TaskCreate & co. and EnterPlanMode have their raider
   tools. ADR 0025 lists every known Claude Code tool name and why the
   others (NotebookEdit, ToolSearch, SendMessage, Monitor, EnterWorktree,
   ...) stay unknown.
 - TaskCreated and TaskCompleted hooks (Claude layout, ADR 0022 addendum):
   task_create and task_update run them before the change, with task_id,
   task_subject and task_description; exit 2 undoes the change and the
   model reads "TaskCreated hook error: STDERR". todo_write fires none. A
   subagent's own task list fires them too, with its agent_id, agent_type
   and permission_mode; their reports go to its journal.
 - A resumed (--continue, --resume) or forked session gets its task list
   back from the journal's last todo.updated (not after /clear; ids
   continue). Only for the task tools.

 [Refusals, web tools and skills like Claude Code]
 - INCOMPATIBLE: a PreToolUse hook's denial reads as in Claude Code: exit 2
   gives "PreToolUse:Bash hook error: STDERR" (tool in Claude's name), a
   JSON permissionDecisionReason is handed through as it stands, no reason
   "PreToolUse:Bash hook blocked the tool call". A call to a tool that is
   not offered (never, or since /reload or a mode change) is answered at
   once, before the hook, the permission gate and any approval, with
   "<tool_use_error>Error: No such tool available: X</tool_use_error>" and
   " Tool names are case-sensitive: call Y instead." when only the case
   differs. The old "denied: PreToolUse hook: ..." and "unknown tool X" are
   gone.
 - INCOMPATIBLE: refusals read as in Claude Code (ADR 0026). The person's
   no: "The user doesn't want to proceed with this tool use. The tool use
   was rejected ... STOP what you are doing ..." or, with a reason, "...
Read more

0.503

Choose a tag to compare

@Getty Getty released this 01 Oct 21:45

Dist::Zilla release