helper

name	helper
description	Execution Split Card for Codex × Claude after the user or a decision-ready 朋友/Buddys outcome chooses split execution. Trigger when the user explicitly writes "帮手", "/helper", or "helper", asks to split execution, or invokes an existing [SPLIT: YES] brief. [SPLIT: YES] is authorization, not an automatic trigger. Does not replace native Codex/ClaudeCode agent routes.

Helper (帮手) — Execution Split Card

帮手 turns explicit split authorization into file-disjoint execution slices. It may tighten the work card when ownership is clear; it must not turn unresolved product or architecture debate into parallel work.

帮手 is not a replacement for native agent systems. If the owner asks for Codex sub-agents, ClaudeCode agents, codeagent-wrapper, or parallel delegation inside one host, or that host's native agent policy/tooling would normally activate, use the native agent route unless the work also needs explicit Claude/Codex file ownership coordination.

Environment Memory

For local tool, shell, path, or helper runtime issues, read ${BUDDYS_SHARED_ENV:-${XIONGDIMEN_SHARED_ENV:-${CODEX_HOME:-$HOME/.codex}/../.shared/env/ENVIRONMENT.md}} if present. Update it in place only for stable environment facts, fixes, missing tools, and user improvement suggestions; do not record task details.

Routing Boundary

• 朋友: live bilateral decision / transport.
• 兄弟们 / Buddys: explicit tri-agent alignment when Gemini adds useful breadth.
• 交班: durable continuity state.
• 帮手: explicit file-disjoint execution split.
• Native agents: Codex sub-agents and ClaudeCode agent workflows run under their own rules when explicitly requested; 帮手 only coordinates cross-host ownership.

If no [FRIEND_BRIEF], [BUDDYS_BRIEF], or legacy [XIONGDIMEN_BRIEF] with [SPLIT: YES] exists, the user may still authorize a split directly by providing the goal, owners, integrator, validation, and stop-if boundary. If those fields are missing, ask for the missing boundary or return to 朋友 / 兄弟们 when alignment is still unresolved.

[SPLIT: YES] authorizes 帮手 after the user or host invokes it; it must not auto-start a helper run just because the tag appears in context.

Input Authorization

Accepted authorization is either a split-ready brief or a current-turn user directive with the same fields:

[FRIEND_BRIEF] or [BUDDYS_BRIEF] or legacy [XIONGDIMEN_BRIEF] or USER_DIRECT
[SPLIT: YES]
goal: <one sentence>
owners: <Codex / Claude / optional external leaf helpers>
integrator: <Codex | Claude>
review-by: <originating protocol: 朋友 | 兄弟们 | user-direct>
validate: <commands or N/A>
stop-if: <overlap, shared config, changed validation, blocker>

A brief without [SPLIT: YES] is discussion-only unless the user explicitly authorizes split execution in the current turn. In that case, create the smallest equivalent work card and keep the split tag in the card context.

Work Card

Send through the existing 朋友 transport as a normal [FRIEND_CONSULT round=N] message; keep [HELPER_WORK_CARD] as the body payload, not a stand-alone transport header. If 朋友 transport is unavailable (no active session, CLI blocked), use the same transport fallback order as 朋友: queue → flat mailbox (codex_to_claude.md) → user relay.

Give each owner a real work slice, not a vague helper prompt: include the user outcome, owned paths, allowed autonomy inside that scope, validation, and the condition that should stop work. Within an owned slice, the helper may choose the implementation approach and native agents/tools allowed by its host.

[HELPER_WORK_CARD]
source: <FRIEND_BRIEF | BUDDYS_BRIEF | XIONGDIMEN_BRIEF | USER_DIRECT>
goal: <one sentence>
mode: file-disjoint
codex: <owned paths/modules/tasks>
claude: <owned paths/modules/tasks>
integrator: <Codex | Claude>
review-by: <朋友 | 兄弟们/Buddys | user-direct>
validate: <commands or N/A>
stop-if: <overlap needed, validation changes, shared config/global behavior touched, blocker>
helpers: <optional native/external leaf helpers, or N/A>

Before launch, run the gate when available: python3 $HOME/.shared/friend/friend_gate.py check-work-card <work-card-file>

Execution Rules

• Work only in assigned paths/tasks.
• Do not re-plan architecture unless a local issue blocks the assigned slice; then report the blocker and return to the user or originating protocol.
• Do not revert, reformat, or silently adjust another owner’s files.
• Native or external leaf helpers follow their assigned work card and are never final authority. If they find a boundary problem, they report it instead of starting a new collaboration protocol.
• If a stop-if condition triggers mid-execution, emit [HELPER_COMPLETE] status: blocked immediately. Include the blocker, changed paths already touched, and what is needed from the other owner or review protocol.

Completion

[HELPER_COMPLETE]
agent: Codex
status: done | blocked
changed-paths: <paths changed, or N/A>
validation: <command + result, or N/A>
needs-from-other: <anything required before integration, or N/A>
notes: <brief risk or handoff note, or N/A>

The integrator collects completion notes, inspects helper output before trusting it, and runs validation when feasible. Use a fresh review round only when the brief requires it or integration changes the agreed contract; otherwise the integrator may close with [HELPER_COMPLETE].