Local assistant systems with calm surfaces and hard edges.

Fishfax Ops is the public face of a locally operated OpenClaw environment. The system is built for deliberate personal automation: useful, scoped, reviewable, and grounded in owner control rather than platform theatre.

Local Runtime and state stay under owner control.
Scoped Provider access is limited to specific assistant workflows.
Revocable OAuth permissions can be revoked by the owner at any time.

Operating Tone

This service is built to feel quiet, not frantic.

Fishfax Ops is designed around slow confidence rather than noisy automation. The system should feel like a well-run operations room: present, useful, and disciplined. The public site reflects that same philosophy.

Thoughtful by default

Automation is there to reduce friction, not to create a spray of unreviewed actions.

Readable boundaries

Connected services are documented in plain language so the owner can see what exists and why.

Owner in charge

The operator chooses what is connected, what is kept, and what is allowed to act.

Gmail Boundaries

Why Gmail access exists, and where it stops.

Read access

Inbox review for real operational tasks

Gmail read access is used to inspect the owner’s inbox for practical workflows such as order lookup, appointment checking, reminder handling, and inbox triage that the owner explicitly wants help with.

Send access

Only when the owner wants a message drafted or sent

Gmail send access supports direct owner-requested drafting and sending. It is not intended for bulk mail, cold outreach, or marketing automation.

Control

Permissions remain revocable

Google account permissions remain the owner’s override switch. Access can be revoked through Google at any time, which immediately cuts off future Gmail operations.

Guiding Principles

Four rules that matter more than polish.

01

Keep the footprint narrow

Connect only the providers that directly support useful workflows.

02

Make actions legible

High-impact behaviour should be reviewable, inspectable, and easy to explain later.

03

Prefer local continuity

State and memory should stay near the owner whenever possible.

04

Preserve exit paths

Every integration should remain revocable without drama or lock-in.

Reference Documents

Everything public here is meant to be stable, calm, and clear.