ThinkForge Mobile is a local-network remote control for the desktop's active project and deployed tools. The desktop remains authoritative for project identity, documents, filesystem writes, SK Memory, credentials, and execution.
Connection Model
The Mobile Dashboard uses an encrypted local connection and automatic discovery. It does not run tools on the phone or through a cloud relay.
Both devices must be able to reach each other on the local network.
Which Tools Appear
Mobile lists tool deployments that:
- Reference an existing tool
- Are global, or scoped to the currently active project
A run also requires both the deployment and the underlying tool to be active.
Mobile works with deployments, not bare tools, because context, scope, model routing, and placement all belong to the deployment.
Available Operations
From mobile you can:
- List visible deployments
- Get a deployment's details, steps, context, and readiness
- Start a run
- Check a run's current state
- See recent runs
- Request cancellation
- Respond to a pending approval
Context Modes
A run uses one of two modes.
Configured uses the deployment's saved Input Sources, Reference entries, and Output Folder.
Override accepts temporary input documents, reference documents, and an output folder for that run only.
Beta limitation: Reference content is not read in either mode. The run emits a warning and ignores those sources.
Run Lifecycle
A run reports queued and running progress, the current step, output messages, final output, error text, approval state, and output documents.
Guided tools and interaction steps can present an approval request to mobile. The run waits until you approve or reject — mobile execution does not auto-approve the way headless surfaces do.
Cancellation is cooperative. It is observed between steps, so an active skill must finish first.
Readiness Checks
Readiness checks are narrow. They report:
- An inactive tool or deployment
- A tool with no steps
- Saved document or folder context that no longer exists on the desktop
They do not validate connected-service credentials or every required skill setting before a run.
Project Safety
Every operation verifies the expected project against the desktop's active project. If the project changes during a request or run, the operation is rejected or cancelled rather than silently acting on a different project.
Limits and History
At most 8 mobile runs can be active at once, and up to 100 recent runs are retained.
These are not a durable execution history. They do not survive an application restart.