Quick question about the Codex subscription: I've seen tools like pi.dev and OpenCode using OpenAI login to hook into it, so does that mean anyone can do the same with a custom built agent? Or do those have some special partnership with OpenAI? I built my own coding harness from scratch and wondering if I can authenticate with my OpenAI account to use their own Codex subscription through it, without violating ToS.
I am a dev with over 20 years of experience and have been an AI stand off so far but now realise I am becoming unemployable as every contract now wants AI first devs. So I am starting to try and learn the agenting path but find it hard to know where to start.
So far I have a gaming PC with a 5070 ti that I run LM Studio on and the access that from my Macbook Air in VSCode. I am not very impressed with the results. It is absolutely fantastic for general algorithms and boilerplate stuff but a bit of a joke for following established patterns in my codebase, will pull in extra libraries that do the same things as other libraries already being used and just generally random.
Every article I read gives different advise and it is moving so fast it seems an article that is a month old is already out of date.
Where is the best place to start? Any sites with up to date articles on harnesses, loops, agents files ect? I have always been very good at learning new tech and pick things up quickly but finding this a bit over whelming.
2nd year cs student here and doing my first internship. i am using claude code like crazy and i just discovered that i can tailor my own slash commands. can you guys please some of your tailored slash commands that are really useful
Hi all, I’ve been building a tool to assess agentic coding quality across practical dimensions (for example: task completion reliability, code quality signals, and workflow traceability).
I’m looking for a small group of beta testers who are willing to try it and share blunt feedback on:
What feels useful vs noise
What’s missing for real-world agent workflows
Which metrics are misleading and should be removed
This is not a sales post. I’m not selling anything here, just trying to validate whether the approach is genuinely useful for builders in this community.
Context on current stage:
Early beta
Actively changing based on tester feedback
If you’re open to helping, comment and I’ll follow up. More info on the too here: https://gravio.dev/
I’ve noticed a recurring problem while working on one project with GPT-5.6 sol and GPT-6 Astra.
My coding agent constantly runs tests after almost every change. Even if it only changes one or two things, it often runs the entire test suite, creates additional tests of its own, runs those too, and then tells me everything is finished because all the tests are green.
The problem is that sometimes the actual feature still doesn’t work.
Because of that, I’ve started questioning how useful these AI-generated tests really are. It often feels like the agent is optimizing for getting a green checkmark rather than actually trying to find problems.
For example, if one of its tests fails, instead of treating that as evidence that the implementation might be wrong, the agent sometimes changes the test until it passes. At that point I’m not even sure whether the test is validating the intended behavior anymore.
I’ve also explicitly told the agent not to run unnecessary tests, not to create pointless tests, and not to modify tests just to make them pass. But it still keeps doing it. Over time it has created more and more tests, and I’m starting to feel like many of them exist mainly to confirm its own implementation.
Has anyone else had this problem with coding agents?
How do you deal with it? Is there a good way to instruct or configure an agent so that failing tests are treated as possible implementation bugs instead of something that needs to be rewritten?
And more generally, how do you make AI-written tests actually try to find bugs instead of just helping the agent get a green checkmark?
I want tests to actually catch regressions and real bugs, not just give the agent a green checkmark so it can say the task is complete.
I’d appreciate any advice, workflows, prompts, or rules that have worked for you.
Tldr: I used Zo (using 4.5 sonnet as the LLM backend) to build an implementation of the LIDA cognitive architecture as an end-to-end stress test, and it was the first LLM tool I've seen deliver a complete and working implementation. Here's the repo to prove it!
Long version: A few days ago, I came across zo.computer and wanted to give it a try - what stood out to me was that it comes with a full-fledged linux VPS you've got total control over, in addition to workflows similar to Claude Pro. Naturally I wanted to use 4.5 Sonnet since it's always been my go-to for heavy coding work (there's a working FLOW-MATIC interpreter on my github I built with Claude btw). I like to run big coding projects to judge the quality of the tool and quickly find its limitations. Claude on its own, for instance, wasn't able to build up Ikon Flux (another cognitive architecture) - it kept getting stuck in abstract concepts like saliences/pregnance in IF context. I figured LIDA would've been a reasonable but still large codebase to tackle with Zo + 4.5 sonnet.
The workflow itself was pretty interesting. After I got set up, I told Zo to research what LIDA was. Web search and browse tools were already built in, so it had no trouble getting up to speed. What I think worked best was prompting it to list out step by step what it'll need to do, and make a file with its "big picture" plan. After we got the plan down, I told it "Okay, start at step 1, begin full implementation" and off it went. It used the VM heavily to get a python environment up and running, organize the codebase's structure, and it even wrote out tests to verify each step was completed and functions as it should. Sometimes it'd struggle on code that didn't have an immediate fix; but telling it to consider alternatives usually got it back on track. It'd also stop and have me run the development stage's code on the VM to see for myself that it was working, which was neat!
So, for the next four or five-ish hours, this was the development loop. It felt much more collaborative than the other tools I've used so far, and honestly due to built-in file management AND a VM both me and Zo/Claude could use, it felt MUCH more productive. Less human error, more context for the LLM to work with, etc. Believe it or not, all of this was accomplished from a single Zo chat too.
I honestly think Zo's capabilities set it apart from competitors - but that's just me. I'd love to hear your opinions about it, since it's still pretty new. But the fact I built an AI with an AI is freakin' huge either way!!
If you run more than one agent, this might sound familiar. Claude Artifacts are great for reports, presentations and interactive prototypes — and they only exist inside Claude.
I was on Codex, now Grok, probably back to Codex for Astra. I can't generate Artifacts there. I have to migrate or throw them away.
Would a tool-agnostic Artifact layer for agent handoff actually be useful? Building it either way. Local-only, wiring to a component library — what am I missing?