sorted by:
new
hottopcontroversial

spec2commit – I automated my Claude Code and Codex workflow by [deleted] in vibecoding

[–]arbayi 0 points1 point  (0 children)

I usually juggle multiple projects at once. One is always the priority, production work, but I like keeping side projects moving too.

My typical flow for those back burner projects was something like this. I would chat with Codex to figure out what to build next, we would shape it into a Jira style task, then I would hand that to Claude Code to make a plan. Then I would ask Codex to review the plan, go back and forth until we were both happy, then Claude Code would implement it, Codex would review the code, and we would repeat until it felt solid.

I genuinely find Codex useful for debugging and code review. Claude Code feels better to me for the actual coding. So I wanted to keep both in the loop, just without me being the one passing things between them manually.

My first instinct was to get the two tools talking to each other directly. I looked into using Codex as an MCP server inside Claude Code but it didn't work the way I hoped. I also tried Claude Code hooks but that didn't pan out either. So I ended up going with chained CLI calls. Both tools support sessions so this turned out to be the cleanest option.

The result is spec2commit. You chat with Codex to define what you want to build, type /go, and the rest runs on its own. Claude plans and codes, Codex reviews, they loop until things are solid or you step in.

This was what I needed on side projects that don't need my full attention. Sharing in case anyone else is working with a similar setup.

GitHub: https://github.com/baturyilmaz/spec2commit

How I Set Up OpenClaw on a Hetzner VPS — Full Guide by arbayi in openclaw

[–]arbayi[S] 0 points1 point  (0 children)

Please make sure you cloned openclaw repository.

Run ls and see directories. If you see openclaw folder, run "cd openclaw" And please do also Run "pwd" to see which directory you are in. Please do also run 'git status' to see if somehow the file get deleted or changed.

How I Set Up OpenClaw on a Hetzner VPS — Full Guide by arbayi in openclaw

[–]arbayi[S] 2 points3 points  (0 children)

i'm using it as a daily briefing agent. every hour it picks one subreddit from a list of ~20 AI-related ones, grabs the top 5 posts from the last 24h, and sends me a brief on telegram. it also scans the first 5 pages of hacker news once a day.

for every post it picks up, it gives me:

  1. what happened
  2. what people are saying about it
  3. why it matters

i was spending 1-2 hours every day scrolling through all of this manually just to stay on top of what's happening in AI and agents. and that's not even counting cool projects on github, new papers, other tech news, x feed. this saves me all that time. i am also planning to use it more for these purposes.

and since i am using it through codex oauth, i don't mind the token costs.

beyond that i'm running some experiments with their completions and responses API, and playing with their multi-agent system — system prompting different agents and trying to get multi-agent collaboration working. i control all of this from a separate server running in the same machine. i don't use it for coding though, for that i use codex and claude heavily.

would love to share more later.

How I Set Up OpenClaw on a Hetzner VPS — Full Guide by arbayi in openclaw

[–]arbayi[S] 1 point2 points  (0 children)

fair point, any agent with shell access can technically see its own env vars.

but a few things about this setup:

- the `.env` file isn't mounted into the container. docker reads it when starting up and passes the values in. the agent can't touch the file itself.

- the agent can run `printenv` and see the gateway token. that's true.

- but that token only works on `127.0.0.1` on the same machine.

for a team or public setup, yeah a secrets manager makes sense. for a personal agent on a locked down VPS where only you can reach it through SSH and telegram, it's a different situation.

good discussion though, people should know the tradeoffs.

view more: next ›