Running a local glm 5.3 with the openclaw agent to code 24/7—is this workflow outdated?
One developer uses the openclaw agent to pick up tasks in a chat room, with the PI coding agent doing the actual coding. They run glm 5.3 locally and occasionally bring in frontier models for review, plus ChatGPT 5.6 sol for brainstorming and spec writing. Tasks are tracked in a self-hosted Gitea repo.
I've worked on a SaaS application for a month now. I have an openclaw agent that I talk to in a chat room and a PI coding agent who does the actual coding. I use a local model (glm 5.3) with occasional frontier model reviews and this has proven sufficient so far and I'm happy with the results. I use chat gpt 5.6 sol on high for brainstorming and speccing features and log the work as issues in a self hosted Gitea repository. There have been some hiccups with openclaw at times but it's now quite stable and coding is basically happening 24/7 as long as I keep a backlog of issues (which I do) as the agents pick up the issues one by one.
What I am wondering is if this is actually old school / suboptimal and if I moved my codebase to github and connected Claude Code I could get things done even faster? I see people talking about spinning up lots of agents at the same time for example. Or maybe opus 5.5 would churn through my backlog at a much faster rate than the local model. I just don't want to get left behind here and I have this nagging feeling that my workflow is old school and slow at this point.
Source: Reddit · ClaudeCode / Codex / VibeCoding · reddit.com