FenceTheCodeTest checkout — $4.99
LOCAL CODE. YOUR CALL.

Safely connect
Codex to
approved
local code.

Connect your project and let Codex request your latest saved code on demand. No ZIP uploads. No repeated copy-paste. You choose the approved folders.

Get FenceTheCode — $4.99 one-time

Launch price for the first 100 customers.

7-day refund policy

Test checkout · No real purchase.

Explore the user guide
Supported now
Codex / ChatGPT Desktop

Windows app · Writes with approval

Coming soon
Claude Code support

Not currently supported.

YOUR WORKSPACE, WITH LIMITS.
FenceTheCodeILLUSTRATIVE PREVIEW
APPROVED PROJECTWRITE WITH APPROVAL
my-projectC:\Projects\my-project
src/Approved scope
app.js✓ Allowed
.env× Protected
private-key.pem× Protected
EXAMPLE REQUESTPropose an edit to src/app.js
Awaiting your reviewNot applied
Local MCP connectionWindows

Only approved code requested by Codex is shared with the AI.

Your project stays local.
Your boundaries stay clear.
No GitHub requiredNo cloud code storageLatest saved local codeWrites with approval
THE PROBLEM / KEEPING CODE CONTEXT CURRENT

Your code keeps changing.
Sharing it shouldn’t mean starting over.

Copying snippets and uploading ZIPs takes time, becomes outdated after edits, and makes you responsible for keeping sensitive files out.

  • 01
    Another edit. Another upload.

    Shared snapshots can fall behind as soon as you save a change.

  • 02
    Useful context takes effort.

    Picking and pasting files interrupts the work you want help with.

  • 03
    Private code needs boundaries.

    Project context can include files and secrets you did not intend to share.

MEET FENCETHECODE

Connect your project.
Share the code Codex needs.

FenceTheCode connects Codex to approved local folders, so it can request your latest saved code on demand.

✓ No ZIP uploads✓ No repeated copy-paste✓ Latest saved files

You choose the boundary.
FenceTheCode checks the requests.

Folder restrictions and protection rules block sensitive files, detected secrets, and outside-folder access. An activity log shows what was allowed or blocked.

Only approved code requested by Codex is shared with the AI.

See how it works
PRODUCT WALKTHROUGH

See FenceTheCode in action.

A walkthrough of connecting a project, reading saved code, and reviewing proposed changes.

FENCETHECODE / WALKTHROUGH
Your project. Your boundaries.Video walkthrough coming soon
Video coming soon.
01 / LESS SETUP. MORE CONTEXT.

One folder.
Three steps to useful help.

Work with the project already on your computer. No repository upload to GitHub.

01

Choose your folder.

Select a local project and review its access settings. Everything outside the approved boundary stays out of reach.

02

Connect to Codex.

Connect the local MCP server to Codex in ChatGPT Desktop. Your files stay in your existing workflow.

03

Ask with context.

Request relevant saved files, then inspect allowed and blocked requests in the activity log.

02 / A BOUNDARY YOU CAN SEE

You choose the boundary.
We check the requests.

You decide where Codex can look. FenceTheCode checks the requests against your project boundary and protection rules.

Approved folders.
Nothing outside the fence.

Choose your project folders. Requests beyond those boundaries are blocked.

Approved projectsrc/app.js ✓Outside-folder request → Blocked

Keep sensitive files out.

Protection rules block sensitive files and detected secrets, including .env files and private keys, and restrict ignored folders.

.envprivate keysignored folders

Review requests. Approve changes.

Review allowed and blocked requests in the activity log. In Write with approval mode, inspect proposed changes and apply the ones you approve in FenceTheCode.

See how the log works ↗
BUILT FOR PEOPLE WHO BUILD LOCALLY

Your project.
Your way of working.

FOR DEVELOPERS

Private code. Focused help.

Give Codex useful context from your project without putting the repository on GitHub.

FOR VIBE CODERS

Build with a clearer boundary.

Work with saved local files and understand what the assistant is requesting.

YOUR FIRST REQUEST STARTS HERE

A guide that gets to the point.

From selecting a project to reading a file and checking the activity log.

Open the user guide
03 / LAUNCH OFFER

Start with a clearer boundary.

Windows · Codex / ChatGPT Desktop

Checkout and delivery are handled through Dodo Payments.

04 / THE DETAILS

Good questions.
Straight answers.

Can I get a refund?

Yes. Request a full refund within 7 days of purchase. This is in addition to any rights you have under applicable consumer law. See the Refund Policy link in the footer for instructions.

What code is shared with the AI?

Only approved code requested by Codex is shared with the AI. Your project remains local. Shared content is subject to the AI provider’s policies and your account settings.

Do I need GitHub?

No. Work directly with approved local folders on your Windows computer. FenceTheCode does not provide cloud code storage.

Will Codex see my latest changes?

Yes, after you save them. FenceTheCode reads the latest saved contents of allowed files on demand.

What does FenceTheCode block?

Protection rules restrict .env files, API keys, private keys, ignored folders, and requests outside approved folders. Review your folder selection and protection settings before sharing code.

Can Codex edit my files?

Yes. In Write with approval mode, Codex can propose changes for you to review and apply in FenceTheCode. Read-only mode remains available.

YOUR CODE. YOUR BOUNDARIES.

Give Codex the right code.
Keep the boundary yours.

Get FenceTheCode — $4.99 one-time

Launch price for the first 100 customers.

7-day refund policy

Test checkout · No real purchase.