Overview
Actions turn repeated terminal input into a named, one-tap operation. An Action can open an interactive agent terminal, run a short command and return its output, or start a long-running script in a tmux-backed background session.
Choose Interactive for Claude Code, Codex, OpenCode, and other TUI programs that need continued input. Quick Task is designed for synchronous commands whose result you want to inspect immediately. Background Long Task keeps time-consuming work running remotely while exposing saved and live logs.
When to use it
- Launch an agent with the exact resume flags, model options, or environment variables required by a repository.
- Run lint, unit tests, type checks, Git status, service health checks, or release verification and review the output as a task result.
- Start long builds, integration suites, data processing, deployments, or log followers that must continue when Redock disconnects.
- Give teammates or your future self a clearly named entry point instead of relying on shell history or remembered commands.
- Separate interactive, quick-result, and background execution so each command opens in the interface best suited to its behavior.
Resume an agent correctly
Save the repository path, resume flag, model choice, and environment setup in one Interactive Action. From a phone, one tap opens the same agent workflow without reconstructing a long launch command.
Turn verification into a result
Use a Quick Task for lint, unit tests, type checks, Git status, or service health. The command finishes synchronously and its output remains available for review instead of disappearing into terminal history.
Run work that outlives the phone
Start a build, integration suite, deployment, migration, or data job as a Background Long Task. It continues through app suspension or disconnects, while saved and live logs show its progress.
How it works
- Create an Action and choose its Host or Project context.
- Enter the command and select interactive, quick-task, or background mode.
- Run it from the workspace and return to its session or result later.
Practical guidance
Use clear names such as “Run unit tests” or “Resume Codex”. Keep destructive production commands out of one-tap Actions unless they include their own confirmation step.