Check the current state
Open the Terminal to see whether the agent is still working, finished, or waiting for input.
Workflows
01 / Work from anywhere
Control AI coding agentsfrom your phone
Claude Code, Codex, and OpenCode keep running on your development machine. After you leave the computer, Redock lets you check progress, answer the agent, add instructions, and keep the active task moving from your phone.
IN THIS WORKFLOW
Start on the development machine, continue from your phone
This workflow explains how a coding agent remains in the real development environment while Redock lets you continue the task after leaving your computer.
- 01
Why AI coding tasks get interrupted after you leave
- 02
How the mobile workflow connects to the development machine
- 03
Which interactions make sense on a phone
- 04
What Redock contributes to the workflow
- 05
A practical example of answering an agent decision
- 06
When this workflow is most useful
00
BEFORE YOU START
Run the coding agent on the real development machine
Redock is a mobile way back into the development environment, not the environment where the coding agent runs. Start with a Mac, Linux host, or cloud server that already contains the repository and its dependencies.
Claude Code, Codex, or OpenCode should already be installed and authenticated. Start the agent in the project directory, then use your phone for later check-ins, replies, and follow-up instructions.
- A development machine that can keep the project and agent running
- A Host and Project already configured in Redock
- Claude Code, Codex, or OpenCode installed and signed in
Development machine terminalshell
cd ~/projects/your-app
# Start the coding agent you use
claude
# Or: codex
# Or: opencodeChoose one agent command. You do not need to run all three.
01
THE PROBLEM
The agent is still working, but you may no longer be at the desk
You ask Claude Code to implement a feature, or let Codex or OpenCode work through a set of changes. Once the task starts, you do not need to watch every line of terminal output.
You may get coffee, go to lunch, take a walk, or start heading home. The agent may continue editing and running checks long after you leave.
Ten minutes later, it may stop and wait for one decision.
How should this edge case be handled?
Should another file change too?
Is it safe to continue with this approach?
Often, all you need is enough context to send one clear reply.
If every small decision requires returning to the computer, the time saved by the coding agent is gradually lost to interruptions.
The agent stays on the development machine.
You do not need to stay beside the computer.
Reconnect from your phone when the task needs a decision.
02
THE WORKFLOW
Leave the computer without leaving the coding loop
Redock does not move the development environment onto the phone.
The code, Terminal, and coding agent continue running on the Mac, server, or other development host. The phone gives you a way back into the active workflow when needed.
- 01
Start the coding agent
Launch Claude Code, Codex, or OpenCode on the development machine and give it a task.
- 02
Leave the computer
Let the task continue while you do something else.
- 03
Open Redock
When you want an update or the agent needs input, return to the relevant Project and Terminal.
- 04
Continue from the phone
Review output, answer a question, add a requirement, or dictate a short instruction.
Example task for the agenttext
Implement filtering for the user list.
Requirements:
- Sync filters to URL parameters
- Preserve them after refresh
- Run the relevant testsLet the agent continue on the development machine. Open Redock when you need to check progress or provide input.
Return to the same session instead of starting over.
Claude Code and its task context remain on the development machine.
Open the Project and Terminal in Redock to review output or send the next instruction.
03
WHAT TO DO ON THE PHONE
Most check-ins involve only a few small actions
Continuing AI coding from a phone does not mean rebuilding your entire desktop workflow on a small screen.
Mobile works best for short interactions that determine whether the agent can keep going.
Answer one question
The agent may only need a decision about scope, data structure, or UI behavior.
- “Update this component too.”
- “Do not change the database schema yet.”
- “Continue with option B.”
- “Add a loading state here.”
Add one requirement
Ask for another test, an error state, or a mobile check without restating the entire task.
- “Add one more test.”
- “Handle the error state too.”
- “Check the mobile layout as well.”
Use voice when typing is awkward
Dictate a new instruction, review the text, and send it to the agent when a long mobile prompt would be uncomfortable.
Add one instruction from your phone:
Short mobile instructionstext
Continue with option B.
Do not change the database schema yet.
Add a test for the error state.
Check the mobile layout too.
The same mobile entry point can continue OpenCode.
Redock does not bind this workflow to one coding agent.
If the agent runs in the remote Terminal, you can review progress and continue the task in the same way.
04
A COMMON SCENARIO
You leave for lunch while the agent keeps working
In the afternoon, you ask Claude Code on your Mac to add filtering to a user list and check whether related code should change.
The agent reads files, edits code, and runs checks. You leave for lunch instead of watching the terminal.
A few minutes later, most of the work is complete, but the agent needs you to choose how filter state should synchronize with the URL.
Without a mobile path back, the task waits until you return. With Redock, you can make the decision from the existing Project and Terminal.
Claude Code is waitingtext
Should filter state use URL parameters or local state?
The choice affects refresh behavior and shareable links.- 01Open Redock
- 02Enter the Project
- 03Review the question
- 04Reply and let Claude Code continue
Your replytext
Use URL parameters. The selected filters should remain after a refresh.The check-in takes less than a minute.
You are not developing the feature again on the phone; you are providing the human decision the agent needs.
05
HOW REDOCK SUPPORTS THE WORKFLOW
Three capabilities reconnect the phone to the development context
Project, Terminal, and Voice Input work together as one workflow rather than three isolated features.
Project
Return to the right development context
Open the saved host and working directory without rebuilding the context from an empty terminal.
Terminal
Continue the existing agent conversation
Review output and send input to Claude Code, Codex, or OpenCode on the real development machine.
Voice Input
Avoid typing a long mobile prompt
Dictate a reply or follow-up instruction when touch typing is inconvenient.
06
AN IMPORTANT DISTINCTION
The coding agent is not running on the phone
- Mac
- Linux host
- Cloud server
- Other development machine
The development environment remains on your Mac, Linux host, cloud server, or another remote machine.
The repository, dependencies, Git state, and coding agent stay in that environment.
Redock reconnects the phone to the development context; commands are still executed by the original host.
The development environment keeps running. Your phone reconnects to it.
The coding agent, repository, and dependencies remain on the development machine.
Redock returns you to the same Project and Terminal so you can review progress, respond, and keep the task moving.
- 01Development machine keeps running
- 02Phone reconnects
- 03Workflow continues
PhoneRedockDevelopment Machine
07
WHEN IT FITS
Fill the gaps away from the computer instead of replacing it
Longer agent tasks
The agent can work independently but may need a decision later.
Short time away from the desk
Lunch, coffee, meetings, and errands should not keep you tied to a coding task.
Commutes and time outside
Check whether a task finished or answer one simple question.
One small piece of feedback
The response is too small to justify reopening a laptop, but important enough to unblock the agent.
The computer remains the primary development environment. Redock covers the intervals that used to leave an agent waiting.
08
THE RESULT
AI coding keeps moving, and you return only when needed
Remote terminal access asks whether you can open a Terminal from another device.
Remote AI coding asks whether the agent can keep working without you watching it continuously.
Redock focuses on the second question.
The agent stays in the real development environment and continues the task.
You can leave the computer and return from your phone when the agent needs you.
Check the context, send a decision, and continue with your day.
09
COMMON QUESTIONS
Using AI coding agents from a phone
Does Redock run Claude Code or Codex on the phone?
No. The agent runs on your Mac, Linux host, or server. Redock connects the phone to that environment.
Do I need to keep Redock open while the agent works?
Not for the mobile check-in itself. Whether the agent continues depends on the host, process, and session setup. Use a persistent session such as tmux when you expect to disconnect.
Can I use OpenCode with this workflow?
Yes. The workflow applies to terminal-based coding agents running on the configured development host.
Is Redock intended to replace desktop development?
No. The computer remains the primary environment. The phone is useful for progress checks, decisions, and short follow-up instructions.
下一篇 Workflow
Keep long-running coding sessions alive
BUILD ANYWHERE
Leaving the computer does not mean leaving the AI coding workflow
Connect Redock to your development machine and continue Claude Code, Codex, OpenCode, and remote Terminal sessions from your phone.
在 App Store 下载