[FEATURE]:Feature Request: Department-based Session Workflow with Asynchronous Communication #19506

Feature hasn't been suggested before.

• I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Background
We hope the OpenCode development team can add a department-oriented session management feature to enable collaborative workflow scenarios among multiple sessions.
Core Functional Requirements
Session-to-Department Mapping
Allow users to define a single session window as an independent "department", and customize multiple departments by creating multiple session windows. Departments can be assigned specific roles and division of labor to form a structured workflow.
Asynchronous Communication Between Departments
Implement inter-department communication via internal system channels or user-specified inbox files. When Department A completes writing a new inbox file, the system (e.g., Ralph-Loop) shall automatically monitor the idle status of Department B.
Idle Detection & Task Triggering
Once Department B is detected to be idle, the system must immediately notify Department B to check the latest workflow inbox file. When Department B opens the inbox file, it should display the following information clearly:
Job responsibilities
Operational specifications
Specific tasks
A mandatory instruction: Write the task completion result back to Department A’s inbox file to close the workflow loop.
Hierarchical Department Management
If Department B has subordinate departments, it should be equipped with user-defined fixed prompts (e.g., embedded in Ralph-Loop’s configuration). The prompts should include core identity and workflow rules for Department B:
Who you are
Who your superior is and what types of tasks you receive from them
Your own core responsibilities
Your standard operating procedures
Who your subordinates are and what tasks you need to assign to them
Expected Workflow
Department A writes task → System monitors Department B’s status → Trigger notification when B is idle → B executes task per specifications → B writes result back to A’s inbox → Workflow loop completes.