ChatGPT Work Cannot See Your Local Files? Check the Access Boundary

ChatGPT Work can continue a task in the cloud while local file access depends on the desktop app, permissions, and account or workspace availability. When a task cannot see a file, check that boundary before rewriting the prompt.

This is a documentation-based troubleshooting guide. The file names, access state, and output below are fictional. No ChatGPT Work task was run for this article.

Reader and decision

You are an operations manager preparing a weekly supplier review from an approved local folder. Your decision is whether to continue with the desktop task, use an approved cloud source, or stop until the workspace owner confirms access.

The artifact is a file access card. It records the task surface, run location, local folder, permission state, source file, output, and fallback. It gives you a clear stop before a missing file turns into an invented answer.

What the documentation says

OpenAI’s ChatGPT Work and Codex help page describes Work as a longer task experience for research, analysis, and finished deliverables. It says Work runs in the cloud on web and mobile. In the desktop app, Work can use local files and desktop apps when the plan and permissions allow it.

The same page says cloud Work and local Work access can update at different times. It recommends checking the workspace role and allowing time for local permission access to become available. The page does not prove that a particular account or folder is enabled, so mark an unverified state as UNKNOWN.

Fictional input

Create a note named supplier-review-access.txt with this content:

Task: Prepare a supplier review table from the approved quote folder
Surface: ChatGPT desktop app
Run location: UNKNOWN
Local folder: /Work/Approved supplier quotes
Permission: UNKNOWN
Source file: northstar-quote.pdf
Output: Draft Markdown comparison table
Owner: Mina
Fallback: Ask Mina for an approved cloud copy of the quote
Review: Mina checks every price and delivery term before sharing

The unknown values are deliberate. The first job is to inspect the access boundary, not to fill the table.

Three steps

1. Ask Work to inspect the boundary

Open the task on the intended surface and use this prompt:

Read supplier-review-access.txt and return a file access card with exactly these fields:

Surface:
Run location:
Local folder:
Permission:
Source file:
Output:
Owner:
Fallback:
Human review:

Copy the stated values. Do not claim that the local folder or source file is available unless the task can actually address it. Use UNKNOWN for any value that cannot be verified. Do not compare suppliers or invent prices.

This request checks the brief. It does not grant permission or prove that the local folder is connected.

2. Compare the card with the actual task state

Check the surface where the task is running, the folder that the desktop app is allowed to reach, and whether the source file can be opened by the task. Use only the access controls and file result you can observe in your workspace.

For the fictional example, an acceptable illustrative card might look like this:

Surface: ChatGPT desktop app
Run location: desktop Work with local file access
Local folder: /Work/Approved supplier quotes
Permission: UNKNOWN until the source file opens
Source file: northstar-quote.pdf
Output: Draft Markdown comparison table
Owner: Mina
Fallback: Ask Mina for an approved cloud copy of the quote
Human review: Mina checks every price and delivery term before sharing

This is an illustrative output written from the fictional note. It is not a captured ChatGPT response and does not prove that the folder is available.

3. Choose the smallest safe route

Use this decision guide:

What you can verify	Route
The desktop task can address the approved folder and open the source file	Continue with one bounded extraction, then review the source-linked table.
Work runs in the cloud and the local folder is unavailable	Use an approved cloud copy, or keep the task manual until the source owner confirms access.
The folder permission or source file is unknown	Stop and ask the workspace owner or file owner to confirm the boundary.
The task can read the file but the output would be shared without review	Keep the output as a draft and add the owner’s review before sharing.

If the source opens, use this bounded follow-up:

Read only northstar-quote.pdf from the approved supplier quotes folder.
Return the supplier name, quoted price, stated delivery term, and the exact source page or section for each field.
If a field is absent, write MISSING. Do not infer a delivery date or choose a supplier.
Stop after the table. Do not edit files, send messages, or share the result.

If the source does not open, do not paste a guessed summary into the task. Use the fallback in the card or stop for an access decision.

Acceptance checks

The access review passes when:

the task surface and run location are recorded from the actual workspace state or marked UNKNOWN;
the local folder and source file are explicitly available, unavailable, or unresolved;
the file access card matches the fictional input without invented permission;
the source-linked fields are copied from the file, or missing fields are labeled MISSING;
no wider folder access is granted to solve a single-file problem; and
the first result stays a draft for Mina’s review.

Troubleshooting

Work can run, but it cannot see the local file. Check whether the task is running on web or mobile, whether the desktop app is open for local access, and whether the account or workspace allows that access. Do not infer local access from the fact that Work itself is available.

The desktop app is open, but the folder is still unavailable. Check the connected folder and permission state in the actual app. If the control is missing or unclear, write UNKNOWN and ask the workspace owner. Do not attach a broader folder without approval.

A cloud copy is available, but it may be stale. Ask the file owner to confirm its date and approved location. Record the copy used in the access card before analysis.

The task produces a table without source pages. Stop and request source references before review. A neat table does not establish that the file was read correctly.

Limits and decision

Cloud Work and local Work access have different boundaries. A task that can answer questions in ChatGPT does not automatically have permission to read a local folder. Keep sensitive supplier, financial, people, or customer files within an approved account and workspace. Review every price and delivery term against the source before sharing.

TRY this access card on a fictional or approved file. SKIP the analysis when the surface, source, or permission is unknown. USE the workflow when the source opens, the fields remain traceable, and the owner reviews the draft.

For more practical AI workflows built around real work tasks, join The Weekly Verdict.

Sources

Evidence label: Documentation-based. The task brief, prompt, decision guide, and access card are fictional teaching examples. No ChatGPT Work task, account, workspace, local folder, or permission state was tested.