Workspace Viewer

Read-only local workspace access for ChatGPT through a custom GPT and local Agent.

Available as a custom GPT

Workspace Viewer is currently available as a custom GPT. Open it in ChatGPT, or mention @Workspace Viewer in a normal ChatGPT conversation to list workspaces, create an Agent pairing code, and inspect approved local workspaces.

Open Workspace Viewer GPT

The ChatGPT App version is not published yet. The current release uses the custom GPT with GPT Actions and the local Agent CLI.

What it does

Workspace Viewer lets ChatGPT inspect local workspaces that you explicitly register through a local Agent. It is designed for read-only project understanding: listing workspaces, summarizing directory structure, reading bounded text excerpts, searching files, and batching several read-only inspections into one request.

Core boundary: workspace root paths stay on your device. The hosted service stores workspace summaries and relays authenticated requests to your Agent; it is not a general remote file manager.

How it works

1. Open the custom GPT

Open Workspace Viewer GPT, or mention @Workspace Viewer in a normal ChatGPT conversation.

2. Create a pairing code

Ask Workspace Viewer to create a short-lived Agent pairing code, then use it from the local Agent CLI to connect your machine.

3. Register workspaces

Add one or more local folders to the Agent. Only configured workspaces are eligible for read-only inspection.

4. Ask ChatGPT

Ask Workspace Viewer to list, search, summarize, or inspect files from registered workspaces.

Capabilities

List connected workspaces and whether their Agent is online.
Summarize a workspace at low cost before reading deeper files.
Inspect directory trees with bounded depth.
Read bounded ranges from text files.
Search file paths or file contents inside approved workspaces.
Batch multiple read-only inspections into one request.

Safety model

Read-only: the App does not edit or delete local project files.
Workspace-scoped: inspection is limited to folders explicitly registered in the local Agent config.
Path-guarded: requests are constrained to approved workspace roots.
Authenticated: App access uses OAuth and paired Agent credentials.
Minimal server metadata: workspace root paths remain local to the Agent.

Support

Questions, access requests, or policy inquiries can be sent to slhafzjw@slhaf.work.