Connect your phone and PC to an AI assistant.

Before you begin

• Use only an official, verified Forge build. Never install an APK from an unknown sender.
• Have an Android phone that supports the released app and, for PC workflows, a supported Linux PC. The PC companion is currently Linux-first, not yet a verified Windows/macOS installer.
• Have a compatible AI client and a network connection for remote MCP access. Local app building does not require cloud AI inference.
• Enable developer/USB debugging only for initial advanced-helper provisioning on a PC you trust. Disconnect or disable debugging afterwards if you do not need it.

Step 1 — Install Forge and inspect its controls

1. Install the official signed Android APK and verify its published SHA-256 value.
2. Open Forge and select Connect. The service status shows when an HTTPS connection is established.
3. Leave Advanced phone access OFF until you explicitly need screenshots, logs, shell commands or installs.
4. Open Forge privacy & safety policy from the app and read what is transmitted through your AI provider and chosen relay.

Preview limitation: there is no publicly verified Forge APK download or published Python companion package yet. This guide describes the planned supported flow, not a promise that a public install is presently available.

Step 2 — Choose your AI client

ChatGPT

Connect the Forge MCP URL through the supported ChatGPT connector/plugin workflow. Sign in with the one-time code generated on your phone, check the requested scopes, and only grant the access you need. Public listing remains subject to OpenAI's review.

Claude

In Claude, add a custom remote MCP connector with the Forge HTTPS MCP URL. Claude supports remote MCP and its OAuth callback must be specifically allowed by Forge. The callback is supported in the upcoming integration build; end-to-end Claude testing is still pending. Follow Claude's connector instructions.

Gemini CLI

The Gemini CLI uses a configured MCP Streamable HTTP endpoint, plus a local browser callback when OAuth is enabled. Forge's future integration permits only its documented loopback callback, bound to PKCE. After release, a configuration could look like:

gemini mcp add -s user -t http saient-forge https://YOUR-OWN-FORGE-ENDPOINT/mcp
gemini mcp list
# In Gemini CLI, use /mcp auth if OAuth sign-in is required.

Do not use the existing Saient internal relay URL as a shared public endpoint. See Gemini CLI's official MCP guide. Gemini provider compatibility is under test and not a guarantee of support in every Gemini product.

Step 3 — Pair your PC without Docker

The existing PC companion is a Python project with a command-line entry point and local UI. The public distribution target is an installable Python package named saient-forge-pc so customers don't need Docker, manual repository checkout or service configuration. It has not been published to PyPI yet.

After publication and platform validation, the intended command will be:

pipx install saient-forge-pc
forge-pc setup
forge-pc status

During internal testing, use the verified Forge PC source supplied directly by Saient. On the PC, choose Phone link → Generate pairing code. On the phone, open PC link, enter the code locally and confirm the pairing. Do not paste the code, private keys or account passwords into an AI conversation.

The PC companion runs as your own operating-system user. Tool access is not an OS sandbox; do not grant full access on a machine you do not control. Windows/macOS packages and a simplified production installer are separate validation milestones.

Step 4 — Choose where the endpoint runs

Execution: Forge commands, builds and file operations run on your phone or PC, using the account and permissions you authorised. Saient does not need a central GPU server to execute your shell commands.

Connectivity: cloud AI clients need a reachable HTTPS MCP endpoint. The current internal setup can use a private, owner-configured HTTPS tunnel or relay. A production multi-user relay would require separate customer isolation, authentication, abuse controls, monitoring, deployment and pricing. It has not been launched.

Website: saient.co.uk provides documentation and downloads. saient.co.uk/forge is an internal service/API route, not a user-facing app page or a reusable connection for every customer. Per-user public onboarding URLs will be documented once the hosting plan is finalised.

Step 5 — Use permissions and emergency stop

1. Grant a read-only connection before giving an assistant build or device scopes.
2. When an assistant requests an arbitrary Android shell command or remote APK install, inspect the exact command/file hash on the phone.
3. For high-risk operations, Forge requires explicit phone confirmation and your real Android screen lock. Decline any action you do not understand.
4. Use Stop connection, Advanced phone access OFF, OAuth sign-in revocation, or the PC emergency pause to shut down access. Completed changes cannot be undone automatically.

Troubleshooting and support

• Start connection stays highlighted? The next Android UI update disables the Start button while connecting or connected and changes the label to a connection status.
• Sign-in fails? Use a fresh one-time phone code, the same MCP resource/URL, and the exact provider callback supported by the release.
• Phone helper is unavailable? You may need to unlock the phone and complete owner-authorised initial USB provisioning. A restart may require authorized USB recovery.
• Tool result missing? Check Forge's request state; pending owner approvals expire and do not execute automatically.

Contact Forge support for preview issues. Do not attach credentials, full private logs or screenshots containing personal details without reviewing them first.

Important notice

AI can be wrong. Review code, commands and generated outputs before using them. Saient provides Forge's connection and device tools but does not control independent third-party AI model outputs. This does not remove Saient's legal obligations or your statutory rights. Read the Forge privacy & safety policy.