Skip to content

rundesk-ai/rundesk-cli / src/skills/managing-rundesk

managing-rundesk

Verified

Use when managing this agent, any other agent in its Rundesk install, or the install itself. It supplies verified operational workflows and safety rules for agent instructions, gateways, conversations, channels, schedules, providers, skills, backups, configuration, credentials, and the Rundesk lifecycle. Do not use for ordinary project work or for deciding, performing, or reviewing delegation.

references/lifecycle.md

View on GitHub
# Install lifecycle

Lifecycle commands manage Rundesk's program tree and launchd jobs. Treat update and removal as
machine-level operations; preserve owner data and report every refusal.

## Commands

| Command | Control |
|---|---|
| `install [--source <dir>] [--bin-dir <dir>]` | Install from a program tree and place the command link in the chosen PATH directory. Defaults use the running source and installer-selected bin directory. |
| `update [--continue]` | Check the published release and move to it, optionally resuming the active originating channel turn after health returns. |
| `uninstall [--confirm]` | Preview removal; `--confirm` removes program, job definitions, and command link while retaining owner data, backups, and credentials. |
| `uninstall --purge [--confirm] [--root <dir>]` | Also remove owner data and the live credential store. A confirmed purge requires `--root` to match `RUNDESK_HOME`; backups, which may contain credentials, are never removed. |

Prefix every command with `"$RUNDESK_COMMAND"` for an existing install. An update may restart the
gateway hosting the current agent; Rundesk queues that restart until the active turn finishes and
then brings the gateway back online.

## Install

- Outside an installed agent turn, explicitly set the intended `RUNDESK_HOME` and pin `--bin-dir`.
  Never assume the default root or write through an unrelated command on `PATH`.
- `--source` must be the Rundesk tree to place. A successful install settles migrations and records
  the command link it actually created.
- Run `status` using the newly placed absolute command. An installer that did not prove the result
  has not completed.

## Update

1. Run `status`, `version`, and `backups save`.
2. Run `update`. For a new release, it cycles every online gateway around the program swap and
   settling, then starts exactly those again. Do not stop them preemptively. An up-to-date settle
   cycles only gateways whose agents still need migration.
3. Preserve all three release answers: moved, already current, or unable to determine the published
   version. Unknown is not up to date. `version` may report UNKNOWN and exit `0` because it answered;
   `update` exits nonzero when it cannot determine what to install.
4. Run `status` and `version` again. Install migrations advance once in `config.json`; each agent's
   migrations advance independently, so one agent's failure need not conceal the others.

Use `--continue` only inside the active channel provider turn that must verify and finish its own
work afterward. It is explicit opt-in: ordinary and automatic updates never wake a conversation.
Rundesk accepts owner guidance already incorporated into that same active turn and binds the handoff
to its latest message. It refuses terminal or ambiguous callers and suppresses a duplicate when
newer owner input or a newer turn already moved the conversation on. It resumes the exact provider session when safe;
otherwise it wakes the same conversation in a fresh session and directs context recovery through
`messages`.

## Uninstall and purge

1. Save and list backups. Run the exact uninstall without `--confirm` and inspect the preview.
2. Use ordinary uninstall unless the owner explicitly requested deletion of data and credentials.
3. Copy the root-bound command from the preview. A confirmed purge refuses a missing or mismatched
   `--root`; do not reconstruct or omit either its `RUNDESK_HOME` assignment or root assertion.
4. Add `--confirm` only after the owner approves the named root and retained/removed categories.
5. Report what was removed and what remains, especially the backup location.

Uninstall stops placed jobs before removing the program. `--purge` is irreversible from the live
install data, but backups survive and can contain recoverable credentials.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall