Getting Started | FenceTheCode

1. Choose your project folder

Open FenceTheCode and select the local project folder you want Codex to access. Review the folder selection and protection settings before sharing code.

Choose the specific project you are working on. Requests outside the approved folder are blocked.

2. Connect to Codex

Connect FenceTheCode’s local MCP server to Codex in ChatGPT Desktop.

Detailed installation and connection steps will be added here after they have been verified against the desktop app.

3. Confirm the approved project

Start with a file listing. Confirm that the connected folder is the project you intended to share.

TRY THIS PROMPT

Use FenceTheCode to list the approved project files. Tell me which project folder is connected. Do not read file contents yet.

Protected entries are excluded from the listing. A missing entry does not prove that the file does not exist.

4. Read saved code

Use the exact project-relative path from the listing. Replace src/app.js below with a file in your project.

READ A FILE

Use FenceTheCode to read src/app.js and explain what it does.

Save your changes first. FenceTheCode reads the latest saved file contents on demand. Unsaved editor changes are not included.

For a task involving several files, keep the request focused:

FOCUSED PROJECT REQUEST

Use FenceTheCode as the only source of local project context. Read only the allowed files needed to explain this feature. If a file is blocked, continue without it and explain what information is missing.

5. Review the activity log

Check FenceTheCode’s desktop activity log to see what Codex requested and whether access was allowed or blocked.

Allowed

The request passed the applicable access checks.

Blocked

Access was refused. Check the recorded reason before deciding what to do next.

Protection rules restrict sensitive files, ignored folders, and requests outside the approved project. Continue with allowed files rather than trying to bypass a restriction.

6. Review code changes before applying

Use Read-only mode when you only want Codex to inspect code. To work on changes, use Write with approval mode for the approved project.

Ask Codex to propose the changes through FenceTheCode. Review the proposed files and diffs in FenceTheCode, then apply the changes you approve. A proposal in this mode does not change your files by itself.

PROPOSE A CHANGE

Use FenceTheCode to read src/app.js and propose a small improvement. Submit the proposed changes through FenceTheCode so I can review and apply them.

Replace src/app.js with an allowed file from your project. Review every diff, keep appropriate backups, and check the resulting saved code after applying changes.

Troubleshooting

The approved folder changed

Reconnect FenceTheCode, then request a fresh file listing. Confirm the folder before asking Codex to read code.

A file cannot be found

Check the current listing and use the exact project-relative path, including any required subfolders.

Codex sees older file contents

Save the file in your editor, then ask FenceTheCode to read it again.

A request is blocked or not approved

Check the desktop activity log. The path may be protected, ignored, or outside the approved folder. An approval may also have expired or been declined.

FenceTheCode tools are unavailable

Check the FenceTheCode connection in Codex / ChatGPT Desktop. After reconnecting, request a fresh project listing.

Purchase and download

Checkout and delivery are handled through Dodo Payments. For a live purchase, follow the delivery instructions in your Dodo order confirmation. If you cannot access your download, contact us with your order number.

When a checkout is labeled test mode, it is for testing and is not a real purchase.

Need more help?

When reporting a problem, include the app version, Windows version, and relevant error message. Redact credentials, private project content, and personal information before sharing logs.

Email anuragkulkarni4321@gmail.com for setup, purchase, delivery, or refund help.

Back to FenceTheCode ↗