Use Endpoint Local Web

Use this guide when you are at the endpoint computer and need the local Pharaoh control panel for enrollment recovery, diagnostics, redacted logs, or validated local settings.

Endpoint Local Web is local-only. It is served by the endpoint agent on loopback after an explicit open action from the Pharaoh tray or taskbar entry. It is not a public web console route.

Before You Start

The endpoint agent must be installed and running on the computer.
Open the local surface from the Pharaoh tray or taskbar action, such as Open Endpoint Local Web.
If you use a copied local link, treat it as a convenience pointer only. The endpoint still requires an explicit local session opened by the agent, and old links cannot reopen an expired session.

Step 1: Open The Local Session

Open Endpoint Local Web from the Pharaoh tray or taskbar menu. A new local browser session opens to the local status view.

The top bar confirms that the surface is Local only, shows a redacted endpoint identity, and shows the idle window. The default idle shutdown is 30 minutes. Accepted API actions such as refreshing state, changing log filters, exporting logs, or saving settings refresh activity. Passive browser state, static assets, and an open log stream do not keep the server alive indefinitely.

If the local session expires or the agent shuts down the listener after inactivity, reopen it from the tray or taskbar. A stale browser tab should show the expired-session recovery message instead of silently reconnecting.

Step 2: Check Status

Open Status for allowlisted endpoint-local diagnostics.

Status may show operational metadata such as:

local serving state, start time, last accepted API activity, idle timeout, and hard lifetime
redacted endpoint, organization, hostname, backend, and version details
connectivity, active session counts, observation/runtime state, and local runtime health
enrollment state, backend reachability, and redacted local configuration status

Status must not show IT knowledge-base sync/cache/search metadata, knowledge-base article body content, sensitive titles, snippets, raw tokens, raw backend URLs, raw config secrets, or unredacted errors. IT knowledge-base content and search stay backend-owned; Endpoint Local Web only reports local endpoint status, logs, settings, and enrollment diagnostics.

Step 3: Inspect Logs

Open Logs when you need local endpoint-agent logs.

The logs workflow supports refresh, live or paused viewing, search, severity/source filters, redacted export, stream interruption messaging, restart messaging, empty/search-empty states, and long-line wrapping.

Redaction is part of the product contract. Passwords, bearer tokens, API keys, private keys, enrollment tokens, agent tokens, recovery secrets, backend URLs, and raw config secret values must be redacted before logs are shown, streamed, exported, screenshotted, or written into proof artifacts.

An open log stream does not extend the 30-minute idle session by itself. User actions that call APIs can refresh local activity; stream heartbeats and server-delivered log frames cannot.

Step 4: Update Settings

Open Settings only when you need to edit local endpoint-agent configuration from the computer.

Settings use validated form controls rather than raw JSON or YAML. Secret fields are hidden, redacted, or write-only. Pharaoh does not write configuration incrementally while you type.

Use Save after the full draft is ready. Invalid values should show field errors and must not replace the current, desired, or last-known-good configuration. Valid values are written atomically. If a restart is required, the page shows a delayed restart indicator. If the candidate configuration or restart fails, Pharaoh should restore the last-known-good configuration and show the fallback or reverted state near the save result.

Reset local state, Factory reset, and Restart agent are distinct actions and require confirmation before they run.

Installed-host service-manager restart and fallback behavior still requires platform proof on supported Windows, macOS, or Linux hosts before it can be treated as fully proven.

Assistant Policy Boundary

For new organizations and endpoints, Pharaoh enables the backend-owned local assistant policy by default only when an approved default guardrail template can be resolved. Endpoint Local Web does not host chat, local transcript history, or assistant work during outages.

Existing production accounts are not automatically updated by the documentation or local UI. Production updates require explicit approval, production credentials, a dry run, redacted target counts, an applied upsert count, readback evidence, and a rollback note.

What Success Looks Like

You are done when:

the local session opened from the tray or taskbar and landed on local status
status, logs, or settings showed only the data needed for the workflow
sensitive values were redacted in diagnostics, logs, exports, screenshots, and errors
invalid settings were rejected before write
valid settings showed save/restart/fallback state clearly
an idle or expired local session told you to reopen from the tray or taskbar