@simpsoka@TheRealAdamG yes. I’m currently on Plus and have auto reload credits enabled. I’m afraid of using it and waking up to a $5000 credit card bill.
In a non-interactive codex exec CI job, should we check out/copy that skill into CODEX_HOME/skills, install the 3rd party cli, and provide credentials it needs via CI secrets? Or is there a more supported packaging/loading mechanism for repo-hosted skills?
@reach_vb@dkundel@Dimillian@nickbaumann_ what’s the recommended pattern for using a shared Codex skill from another repo in CI/CD (GitLab), when that skill needs to run an underlying CLI tool? 🧵
e.g. I have a Codex skill that depends on an underlying CLI tool to fetch context from an external system before reviewing an MR. Ideally, the skill would live in a shared repo so multiple projects can use it, rather than each project copying it locally.
@ben_j_todd I’m skeptical cause you look pretty young for a lad that had spent 15 years researching. But then, seeing the blurb from Cal Newport had me curious. also, been looking for this book for all my working life! will definitely check this out. thank you for writing this book!
@reach_vb@whoiskatrin I prefer my 5 hr limit to refresh during lunch hours so that I have a fresh window after lunch. for that, I created a weekday automation to run at 8 a.m to pull news headlines around global issues, AI and tech. anyone else does this?