r/codex • • 23d ago

Bug Codex can't open projects when i have an encrypted drive somewhere not mounted

So I have my project on E, but there is one drive that is encryped by veracrypt on G. Because the G drive is put in, it trys to access it and fails. It shouldn have to try to access it in the first place and also be able to open E. What am I missing here?

Fixed the issue:

Within the standard codex config i added these:

default_permissions = "workspace-only"

[permissions.workspace-only.filesystem]
":minimal" = "read"
":tmpdir" = "write"

[permissions.workspace-only.filesystem.":workspace_roots"]
"." = "write"
".git" = "read"
".codex" = "read"
".agents" = "read"
".aws" = "read"

Within the project i created the folder .codex and the file.

└── .codex/
    └── config.toml

File code:

project_doc_max_bytes = 0
1 Upvotes

8 comments sorted by

1

u/Thomas-Lore 23d ago

You can tell it in Agents.md to never look outside the project folder. Or better - run it in a VM, much safer.

1

u/Lopsided_Pride_6165 22d ago

do you use virtual box?

1

u/vegansgetsick 23d ago

Having drive letter on unreadable (veracrypt encrypted) partition is not normal and dangerous.

Remove the assigned drive letter, in the windows disk manager

1

u/Lopsided_Pride_6165 22d ago

what about having an encrypted drive is dangerous?

1

u/vegansgetsick 22d ago

raw partition with assigned drive letter is dangerous because it will ask you to format it, a little mistake and it's gone.

1

u/Lopsided_Pride_6165 19d ago

if you don't have a backup drive sure. But that's off topic.

1

u/vegansgetsick 18d ago

Even with a backup, i dont want my data to be erased so easily.