One OpenCode server. Two useful control surfaces.
KKCode and OpenCode Web can point at the same server, projects, and sessions. The difference is not where the work happens — it is which screen helps you make the next decision.
The shared model
Both surfaces talk to OpenCode running on the machine that owns your workspace. The repository, model credentials, tools, and command execution stay there. A mobile client is not a second agent or a separate copy of your project; it is another way to continue the same work.
That means the best choice is usually about the moment you are in, not a permanent all-or-nothing decision.
Choose the surface by task
| If you need to… | Prefer | Why |
|---|---|---|
| Start a task while at a desk | OpenCode Web | More room to read a prompt, inspect context, and work alongside other browser tools. |
| Watch a long-running task away from the desk | KKCode | The session, tool activity, and status are easy to check on a phone. |
| Answer a question or permission request | KKCode | It keeps the decision and the active session together without reopening a laptop. |
| Review a focused file change | KKCode | Open the file or diff, inspect it, then give a short follow-up. |
| Compare many files, terminals, logs, or plans | OpenCode Web | A larger screen remains better for broad navigation and prolonged investigation. |
| Continue a conversation while travelling | KKCode | A secure remote route makes the same OpenCode session reachable from a phone. |
What mobile is especially good at
KKCode is designed around the handoff moments of agent work:
- Checking whether a task is progressing or waiting.
- Reading the last tool call and changed-file summary.
- Allowing, rejecting, or redirecting a permission request.
- Answering a question that blocks the next step.
- Switching to the right project and continuing an existing session.
- Sending one precise follow-up while the task context is still fresh.
The goal is not to recreate a desktop workstation in a smaller rectangle. It is to keep a useful decision from becoming an unnecessary delay.
What mobile does not replace
Use a desktop surface when the work needs wide comparison, long terminal interaction, conflict resolution, or detailed visual QA. KKCode does not move the project to the phone, and it should not encourage you to treat a phone as a full IDE.
This boundary is a strength: the project environment remains stable on the development machine, while the mobile interface stays quick to open and easy to understand.
A practical rhythm
Start or shape substantial work in OpenCode Web. When you step away, leave the task running and open KKCode only when it needs a glance, an answer, a review, or a concise redirect. Return to the desktop when the task turns into broad investigation.
For the remote path itself, see Remote access. For a focused mobile setup, start with Use OpenCode from your phone.