القائمة
Use when sending a message, context, or instructions to another OpenCode conversation — silent context injection or triggering AI work in a different session.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | session-push |
| description | Use when sending a message, context, or instructions to another OpenCode conversation — silent context injection or triggering AI work in a different session. |
| Mode | Tool call | Behavior |
|---|---|---|
| Context injection | session_push(sessionId, message, noReply=true) | Silent, no AI response |
| Trigger work | session_push(sessionId, message) | AI responds in the target session |
Use project_search to find sessions by keyword. It returns session IDs and titles. Copy the session ID and pass it to session_push.
project_search(query="browser sdk refactor")
→ returns list with sessionId, title, projectName
session_push(sessionId="abc123...", message="Context from another session...")
Each plugin instance watches a file-based push queue for its sessions (~/.local/share/opencode/push-queue/{sessionId}/). When session_push writes a message file, the target session's own plugin picks it up via fs.watch and calls client.session.promptAsync() through the correct server — the same one the TUI is subscribed to. That server fires the SSE event and the TUI updates live.
If the target session is inactive (not open in any terminal), the message file stays in the queue and is delivered the next time that session is opened.
Pushing to the wrong session — use project_search first and verify the title before pushing.
Session is actively running — messages are queued. If the target session is in the middle of a task, the push will be processed after the current task completes.
Use when switching to a different OpenCode conversation, opening a past session in a new terminal, or resuming or forking a session from another project.
Use when querying the OpenCode SQLite database — looking up sessions, searching message content, or converting timestamps. Shared reference for schema and queries.
Use when the user asks to find, recall, or recover a past OpenCode conversation — e.g. "we talked about X earlier", "find that session from this morning", "what did we decide about Y last week"