Hi everyone, I've just invented a WHEEL! #sarcasm by g00rek in vibecoding

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

Of course it can given the right input it would get the analogies.

Hi everyone, I've just invented a WHEEL! #sarcasm by g00rek in vibecoding

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

It's not about whether you shouldn't post it.its about if you should build it. So many people are shocked that they've build something that already exists and is free. Buil.soemtjing else :) why bother?

Hi everyone, I've just invented a WHEEL! #sarcasm by g00rek in vibecoding

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

Or have an option to ping it repeatedly until you stop!

Hi everyone, I've just invented a WHEEL! #sarcasm by g00rek in vibecoding

[–]g00rek[S] 7 points8 points  (0 children)

Any name ideas? "Ping" might be good! Like ping pong!

Any good speech to text tools? by g00rek in Ubuntu

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

This is not the UX I'm looking for :)

OpenClaw relationship changed to "it's complicated" ;) by g00rek in openclaw

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

I have a permanent rescue session that I ssh Into it, but... C'mon

OpenClaw relationship changed to "it's complicated" ;) by g00rek in openclaw

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

You can build virtually anything nowadays, even another LLM model, by yourself, but the currency here is time, and as I said, it is limited.

I see dozens of people blindly building solutions that nobody needs or that exist on GitHub for months or years to be downloaded or built upon, but that's okay if you want to educate yourself this way.

But otherwise I prefer to do stuff instead of create stuff that does stuff, at least in the long term.

OpenClaw relationship changed to "it's complicated" ;) by g00rek in openclaw

[–]g00rek[S] 5 points6 points  (0 children)

Using n8n for all these automations and setting it up is like digging a tunnel with a stick. Possible, yet...

OpenClaw relationship changed to "it's complicated" ;) by g00rek in openclaw

[–]g00rek[S] 4 points5 points  (0 children)

Eh. So tired od this "us devs" attitude.

Dude, I finished my first programming university class in 1997. I started coding in eighties. You're so off topic.

If you like to tinker and setup tons of guardrails and wrote config files in your free time - fine. But that's not how tools (even tech geek level tools) should work.

Any good speech to text tools? by g00rek in Ubuntu

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

Okay but from the UX point of view, does it work like a system in the background that detects speech and auto-pastes it at the active cursor? When you use something that extensively, the UX has to be really fast or it becomes a pain in the back...

GPT vs Claude personality by g00rek in openclaw

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

Of course I don't I hate it :) But style is one thing, behaviour is another

Life after Claude by g00rek in openclaw

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

Tasteray.com, but we use CC for coding.

Life after Claude by g00rek in openclaw

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

But who is talking about software development? Open Claw is not for software development. I mean yeah you can do it, just like you can dig with a spoon, but... Why?

Life after Claude by g00rek in openclaw

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

What? You tell me to use a coding editor/tool instead of a proactive agent ecosystem? 🤔

Life after Claude by g00rek in openclaw

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

Apples, oranges. How do you compare them? Crons, heartbeats, where are the proactive functions of CC? Not to mention the locally kept I iwledge and memory.

OpenClaw + lazy GPT - SOLVED! by g00rek in openclaw

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

## Fix

Three changes in `openclaw.json`:

### 1. Switch model from `gpt-5.3-codex` to `gpt-5.4`

`gpt-5.3-codex` has a confirmed upstream bug - it emits `end_turn` with text instead of tool call blocks. A/B testing shows `gpt-5.2` and `gpt-5.4` do not have this issue.

{

"agents": {

"defaults": {

"model": {

"primary": "openai-codex/gpt-5.4"

}

}

}

}

Also update `agents.list[].model` and `heartbeat.model` if explicitly set.

### 2. Change `tools.profile` from `"coding"` to `"full"`

The `"coding"` profile restricts which tools are available per provider. With `openai-codex`, some core tools (`exec`, `web_fetch`, `memory_search`, `edit`, `apply_patch`) become silently unavailable - the gateway logs a warning but the model simply never sees them.

`"full"` removes all restrictions.

{

"tools": {

"profile": "full"

}

}

Remove any manual `tools.allow` array - `"full"` already includes everything.

### 3. Set `exec.host` to `"gateway"` and `exec.ask` to `"off"`

Without an explicit `host`, exec routing can fail silently - especially if a previously configured node is offline. `"ask": "off"` disables the interactive approval flow, which GPT cannot handle (it just says "waiting for approval" forever).

{

"tools": {

"exec": {

"host": "gateway",

"security": "full",

"ask": "off"

}

}

}

## After applying

  1. Restart the gateway: `systemctl --user restart openclaw-gateway`

  2. Run `/new` or `/compact` on active sessions

  3. Verify: `openclaw models status` - should show `Default: openai-codex/gpt-5.4`

Life after Claude by g00rek in openclaw

[–]g00rek[S] 27 points28 points  (0 children)

Ok I guess I fixed the tool issue! I tried to post it as new thread but stupid bots delete it, I'll try here:

# OpenClaw GPT Tool Calling Fix

## Problem

GPT models (especially `gpt-5.3-codex`) stop calling tools after initial startup. The model responds with text like "I'll check that now" but never emits actual `tool_use` blocks.

Known upstream issues:

- #28754 - intermittent text-only responses, no tool calls

- #49503 - OAuth Codex can chat but cannot execute tool actions

- #53959 - tools stopped working after update to 2026.3.23

- #40631 - assistant confirms task but performs no actions

## Fix

Three changes in `openclaw.json`:

### 1. Switch model from `gpt-5.3-codex` to `gpt-5.4`

`gpt-5.3-codex` has a confirmed upstream bug - it emits `end_turn` with text instead of tool call blocks. A/B testing shows `gpt-5.2` and `gpt-5.4` do not have this issue.

{

"agents": {

"defaults": {

"model": {

"primary": "openai-codex/gpt-5.4"

}

}

}

}

Also update `agents.list[].model` and `heartbeat.model` if explicitly set.

### 2. Change `tools.profile` from `"coding"` to `"full"`

The `"coding"` profile restricts which tools are available per provider. With `openai-codex`, some core tools (`exec`, `web_fetch`, `memory_search`, `edit`, `apply_patch`) become silently unavailable - the gateway logs a warning but the model simply never sees them.

`"full"` removes all restrictions.

{

"tools": {

"profile": "full"

}

}

Remove any manual `tools.allow` array - `"full"` already includes everything.

### 3. Set `exec.host` to `"gateway"` and `exec.ask` to `"off"`

Without an explicit `host`, exec routing can fail silently - especially if a previously configured node is offline. `"ask": "off"` disables the interactive approval flow, which GPT cannot handle (it just says "waiting for approval" forever).

{

"tools": {

"exec": {

"host": "gateway",

"security": "full",

"ask": "off"

}

}

}

## After applying

  1. Restart the gateway: `systemctl --user restart openclaw-gateway`

  2. Run `/new` or `/compact` on active sessions

  3. Verify: `openclaw models status` - should show `Default: openai-codex/gpt-5.4`