#Error creating new session after upgrading to 2026.4.26 (be8c246)

1 messages · Page 1 of 1 (latest)

plush crest
#

13:52:18+00:00 warn agent/embedded {"subsystem":"agent/embedded"} {"event":"embedded_run_agent_end","tags":["error_handling","lifecycle","agent_end","assistant_error"],"runId":"acf714c8-a7aa-45f5-9333-1ccd009789bc","isError":true,"error":"One of "input" or "previous_response_id"or 'prompt'or 'conversation_id' must be provided.","failoverReason":null,"model":"gpt-5.5","provider":"openai-codex","rawErrorPreview":"One of "input" or "previous_response_id"or 'prompt'or 'conversation_id' must be provided.","rawErrorHash":"sha256:f4df43227553","providerRuntimeFailureKind":"unclassified"} embedded run agent end

iron pulsarBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

unreal karmaBOT
#

That looks like an empty first-turn prompt hitting the OpenAI/Codex Responses path.

If this happened right after New Session, /new, or /reset with no extra text, it matches a post-2026.4.26 regression I can see fixed on main but not in the current npm release yet.

Workarounds for now:

  • Start the new session, then send the real message separately.
  • Or use /reset your actual prompt here instead of a bare /reset / /new.

Please also run:

openclaw status --all
openclaw doctor

If it keeps happening on normal non-empty messages too, file it here with that log + status output: https://github.com/openclaw/openclaw/issues

plush crest
#

It worked when I said /new prompt instead of a bare /new. Thanks dude.

unreal karmaBOT
#

Awesome, glad that got you unstuck 🎉

That pretty strongly confirms the bare /new path. Until the next release lands, just include a little text after /new or /reset.

If this fixed it, please right-click the solution message → Apps → ✅ Mark Solution so Answer Overflow indexes it for the next person. 🦐