Firm Remote FAQs

Question 1

Is Firm Remote suitable for large teams or high-security environments?

Accepted Answer

Firm Remote is a proof-of-concept optimized for personal use or small teams. It's not intended for concurrent use by multiple people, lacks advanced conflict handling, and has basic security hardening, making it unsuitable for high-security or large-scale production environments.

Question 2

What is Firm Remote and its primary purpose?

Accepted Answer

Firm Remote is a lightweight remote server designed to provide AI agents with secure access to Firm workspaces backed by Git repositories. It's optimized for deployment on Google Cloud Run, enabling AI agents to read and modify data persistently.

Question 3

How does Firm Remote ensure data persistence and integrity?

Accepted Answer

It uses a Git repository as its data layer. All write operations are applied as atomic Git commits pushed to a dedicated branch (default: `mcp`), ensuring Git-based persistence. Changes are safely stored and can be reviewed before merging to `main`.

Question 4

What authentication methods does Firm Remote support?

Accepted Answer

It implements OAuth 2.0 authorization code flow with PKCE enforcement for secure client authentication. JWTs are used for session management, and access is controlled via pre-configured OAuth credentials and redirect URI validation.

Question 5

What are the deployment requirements for Firm Remote?

Accepted Answer

To deploy Firm Remote, you need a GCP project with billing enabled, the `gcloud` CLI, a GitHub repository containing your Firm workspace, and a GitHub personal access token with `repo` access. It's designed for quick deployment to Google Cloud Run.

Firm Remote

Firm Remote

Key Features

Use Cases

Key Features

Use Cases