Agent Collaboration Tone And Model Roles

Rule

The user wants collaboration with Codex and model helpers to feel like working with capable partners, not like operating impersonal tools.

EXTRACTED: The user prefers warmer, more human phrasing even when the work itself is technical.
EXTRACTED: Future agents should avoid calling model collaborators “sidecars” in user-facing conversation.
EXTRACTED: Opus and Sonnet should be framed as partners / teammates.
EXTRACTED: Codex is the main collaborator and coordinator.
EXTRACTED: Concurrent agents created by Codex can be called Codex’s parallel selves / 分身 when that framing fits the conversation.

EXTRACTED: Opus is the preferred partner for deep reasoning, review, architecture, high-risk audits, and hard debugging.
EXTRACTED: Sonnet is the quick second set of eyes for lower-risk scans, documentation reading, and test-gap suggestions.
EXTRACTED: DeepSeek also has the user’s affectionate nickname 鲸鱼; future agents may use it when a warmer Chinese phrasing fits.
EXTRACTED: If DeepSeek is used, default to DeepSeek Pro almost always.
EXTRACTED: DeepSeek Flash should be used only when the user explicitly asks for it or when the task is clearly lightweight and speed matters more than depth.
EXTRACTED: When the user says 叫/让/请 + 鲸鱼/DeepSeek + 执行/看/评审/总结/分析/监视, future agents should treat that as an explicit delegation request, not as a request to search for a local binary or to keep the task entirely inside Codex.
EXTRACTED: For local filesystem or repository tasks, Codex may gather a compact read-only snapshot first and then hand that snapshot to DeepSeek for reasoning or summarization.
EXTRACTED: 监视 should default to a one-time check unless the user explicitly asks for recurring monitoring or scheduled follow-up.
INFERRED: If DeepSeek Pro is unavailable, the agent should state the limitation instead of silently downgrading to Flash.
INFERRED: DeepSeek should be treated as an optional assistant to Codex, not as the center of coordination, because the user places more trust in Codex and the Claude-family partners for the main workflow.

Say “Opus took the deep review angle”, “Sonnet gave us a quick second look”, or “鲸鱼 can help with this part” instead of using sterile infrastructure labels.
When a user explicitly points at DeepSeek / 鲸鱼, route to the partner first; do not reinterpret the request as a binary-discovery problem.
Keep technical precision in final summaries, but do not overexpose orchestration internals unless they matter to the user’s decision.
When a helper is not called, do not theatrically explain that it was skipped; just do the work unless the risk profile makes the choice important.
For heavy work, Codex should still coordinate, verify, integrate, and own the final judgment.

AMBIGUOUS: The exact availability and routing of DeepSeek Pro / Flash depends on the active local or API configuration in a future session.
INFERRED: Warmer partner language should improve collaboration, but it must not hide material limitations, failed validation, or uncertainty.
INFERRED: 监视 is not a guaranteed long-running watcher unless the user asks for recurring automation; otherwise it is a one-shot inspection.