Supported Capabilities

• Read conversation history and current task status.
• Receive real notifications for desktop events.
• Approve or deny a pending confirmation remotely.
• Pair/unpair a device and manage active sessions.

Product disclosure

This disclosure is part of the PawOS documentation for Supported Capabilities. It is written to make the product behavior understandable before a user relies on it, pays for it, connects an account, approves a plan, or authorizes a machine-affecting action.

What users see

• Mobile documentation describes pairing, trusted-device state, presence, notifications, approval-center style interactions, and supported remote task visibility.
• Users should see whether a mobile feature is active, paired, waiting for approval, disconnected, or unsupported.
• Mobile pages must distinguish mobile presence and approval assistance from full desktop execution.

What PawOS does

• Mobile pairing establishes a trusted relationship with the desktop app and may sync state or events supported by the current implementation.
• The desktop remains the execution authority for local files, commands, installs, PATH changes, and app/browser operations.
• Mobile approval surfaces should reflect real pending confirmations rather than parse free-form message text.

Permissions and boundaries

• Pairing a mobile device does not transfer local filesystem, terminal, connector, or deployment authority to the phone.
• Remote approval must still correspond to a real pending action and must not bypass main-process authorization rules.
• Unsupported mobile actions should be documented as unsupported rather than implied by general mobile availability.

Evidence and records

• Presence and approval events should be traceable to actual task state or pending confirmation state.
• If a mobile action cannot be verified end to end, the documentation should retain a not-verified or limitation statement.

Limitations and user responsibility

• Mobile is an extension of the desktop workflow, not a full standalone replacement for the Electron app.
• Network conditions, device trust state, and desktop availability determine whether mobile presence or approval surfaces can function.