hand-off-a-task
Hand a task to a Rush cloud agent and bring back the result. Use when someone wants work done off their machine or in the background (write tests, upgrade a dependency, research and write a report, investigate an incident), or asks what happened to a task Rush ran earlier.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- hand-off-a-task
- description
- Hand a task to a Rush cloud agent and bring back the result. Use when someone wants work done off their machine or in the background (write tests, upgrade a dependency, research and write a report, investigate an incident), or asks what happened to a task Rush ran earlier.
03 SKILL.md 正文
Hand off a task to Rush
Rush runs the task in its own cloud computer and keeps going while this
conversation moves on. Tool names may carry a client prefix
(mcp__rush__create_session). Never ask for a password, token or API key in
chat, and never report a result Rush did not return.
- Write the task. The session knows nothing from this conversation. Put in
taskthe goal, the files, errors, links and decisions that matter, and what done looks like: "open a pull request", "write the report as report.md", "answer in a few sentences". For code, add "do not merge" unless the person asked for a merge; the agent may otherwise follow merge rules of its own. To build on a finished session, pass its id ascontinue_from; its answer goes at the top of the new task. - Pick where it runs. For code, pass
repo: a GitHub repository, branch (/tree/<branch>) or pull request URL fromlist_repositories, or a gitlab.com project. If the team keeps a Project for that repository (list_projects), passprojectinstead; it brings the Project's standing instructions and secrets. Name a saved agent withagentwhen one fits (list_agents), and the accounts the task may use inconnections(list_connections). Leave out what the task does not need; with noagent, Claude Code does the work. - Start it. Call
create_sessiononce, with a fresh UUID you write yourself asrequest_id(no shell command needed). If the call errors and you retry, send the samerequest_idso only one session starts. For independent tasks, start one session each. - Wait. Tell the person it is running, then call
wait_for_sessionswith every id andtimeout_seconds: 50, again untilsettledis true. A session past the runs-at-once limit startsqueued; keep waiting. With several,until: "any"lets you report each one as it lands. - Read the result.
get_sessionhas the answer, branch, pull request and the files it made.get_session_changeslists the changed files (include_difffor the diff);get_session_artifactreads one file by name. Uselist_session_eventsonly to explain how the agent got there or why it failed. - Continue or stop.
send_session_messagecontinues in the same computer, with its files and conversation, for 7 days after it goes idle; follow it withwait_for_sessions.cancel_sessionstops the session and releases its computer, after which no follow-up is possible; ask before stopping one.
Report each session in a few lines: its status, the answer, and the pull
request or file links. needs_review means Rush could not confirm the result:
say so and show what the agent reported. On failed, give the error and the
next step; do not retry silently.
Work started earlier. When the person asks about Rush work without an id,
call list_sessions (newest first; filter by status), match on the first line
of each answer, then read the one they mean with get_session.
When Rush refuses
A refused call's text starts with a code, and often a Next: step; follow it.
For these, tell the person the fix in one line:
| Code | Fix |
|---|---|
TOKEN_LIMIT_REACHED, CREDITS_EXHAUSTED, SPEND_CAP_REACHED, PAYMENT_METHOD_REQUIRED, COMPUTE_LIMIT_REACHED, WEEKLY_COMPUTE_LIMIT_REACHED |
Relay the message; it names the fix. Model accounts are at https://cloud.getrush.ai/console/settings/?section=accounts and billing at https://cloud.getrush.ai/console/settings/?section=billing |
RESOURCE_NOT_ACCESSIBLE |
Rush's GitHub App does not reach that repository. Add it at https://cloud.getrush.ai/console/settings/?section=connections, or run without repo. |
CONNECTION_NOT_READY |
Call connect_account with type app (gmail, linear, slack, …) or mcp (with its url), and name; for an agent made from a template, also agent. A gitlab.com project needs name gitlab. Give the authorize_url to the person to open in their own browser; never open or fetch it. It works once, for 10 minutes. Start the session again once list_connections shows it connected. |
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.