Setup Codex sandbox

[white238]

This is aimed at a good base for using the Codex Sandbox on LC. I put in effort to allow it to work on non-LC machines but haven't tried it personally. For example, the compute/login node script will default to compute if not on LC and put some guardrails recommended by ChatGPT that might sandbox you outside of a sandbox.

To be very clear, these are here to help but cannot be fully trusted. Only use Agentic AI on repos that you know dont have any work you care to lose since it can still revert/commit/delete.

[tupek2]

If you are interested in getting into the next level of this agentic stuff (which I haven't done yet), I'd recommend you research custom /slash commands (maybe for build or testing), and also the use of LLM hooks (where, for example, you can make a hook that after the agent makes code changes, it automatically builds the code, runs the tests, makes style, etc). Just something to be aware of that I'm not sure the initial tutorial covered. I'm personally more interested in these things than skills, which are mostly ignored.

[tupek2]

Is this likely to default to everyone running debug by default? Its pretty common for people to tell me: 'this or that smith problem is slow' only for me to (after a day of work) realize they were default building debug. Now my default response to these this is: just build in release (which they often still ignore). I personally rarely build, test, or debug in debug. Maybe we want a release_build skill, and a debug_build skill.

[white238]

Swapped to RelWithDebInfo by default unless specifically asked for a debug build.

[tupek2]

Release please. I people want to debug, the should probably run in debug.

[white238]

Maybe we should discuss this in the technical meeting. RelWithDebInfo is nearly as fast (-O2 vs -O3) but does get you debug symbols. I was envisioning these files are mainly for out development. Are you expecting them to be used by people outside of our team? I feel this is a healthy middle ground and if someone really cares they can put it in their agents file or just tell it to use release.

[white238]

I removed the build type from all command except the asan build where i told it to default to debug. I also told it to use the -bt <CMake Build Type> option if asked. I verified it is now finding the skills w/ the new symlink and tested several different variations of prompts and it seems to work like I would expect at this point.

Side thought: I like that I asked codex to make these skills and iterated on them with it.. but it couldn't find them after. It does now.

[white238]

dont merge this.. i just found out its not using my skills and how to fix it.

[white238]

dont merge this.. i just found out its not using my skills and how to fix it.

Fixed now.

[white238]

Example of AGENTS.md that defaults to building debug if that is better for you:

# AGENTS.md

## Build Configuration

Unless explicitly instructed otherwise, always configure and build the project in **Debug** mode.

Do not default to Release or RelWithDebInfo builds.

You can also say "build in debug and with GCC". That worked for me.