Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug] v2026.3.11: register.agent command path doesn't propagate channel + accountId to resolver [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#44452•Fetched 2026-04-08 00:46:49
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
Mdx2025Mdx2025
Participants
Mdx2025Mdx2025

Root Cause

El archivo dist/register.agent-DHoJWl4M.js que registra el comando agent no pasa channel ni replyAccount/accountId en los parámetros al invocar el session resolver. Esto fuerza al resolver a usar fallback a main.

RAW_BUFFERClick to expand / collapse

Bug Summary

En OpenClaw v2026.3.11, el command path en dist/register.agent-DHoJWl4M.js no propaga los parámetros channel y replyAccount/accountId al session resolver, impidiendo el lookup correcto por delivery context.

Síntomas Observados

  • El session resolver no recibe suficiente contexto para buscar por delivery target
  • Los parámetros --channel y --reply-account del CLI no llegan al resolver
  • El resolver no puede identificar la sesión correcta del canal objetivo

Root Cause

El archivo dist/register.agent-DHoJWl4M.js que registra el comando agent no pasa channel ni replyAccount/accountId en los parámetros al invocar el session resolver. Esto fuerza al resolver a usar fallback a main.

Archivo Afectado (dist/ compilado)

  • dist/register.agent-DHoJWl4M.js - Command path sin propagar contexto necesario

Parche Manual Aplicado (Local)

Archivo: dist/register.agent-DHoJWl4M.js

  • Modificado para pasar channel al session resolver
  • Modificado para pasar replyAccount/accountId al session resolver
  • Esto permite que el resolver haga lookup por delivery context completo

Validación Post-Parche

  • ✅ El session resolver recibe todo el contexto necesario
  • ✅ El lookup por delivery context funciona correctamente
  • ✅ Las sesiones se resuelven al canal/thread correcto

Riesgo de Regresión

ALTO: Este es un parche manual sobre archivos compilados en dist/. Se perderá en la próxima actualización/reinstalación de OpenClaw.

Entorno

  • OpenClaw: v2026.3.11
  • Archivo: dist/register.agent-DHoJWl4M.js
  • Fecha del parche: Marzo 2026

extent analysis

Fix Plan

To fix the issue, we need to modify the dist/register.agent-DHoJWl4M.js file to pass the channel and replyAccount/accountId parameters to the session resolver.

Steps:

  • Open the dist/register.agent-DHoJWl4M.js file in a text editor.
  • Locate the function that invokes the session resolver.
  • Modify the function to pass the channel and replyAccount/accountId parameters to the session resolver.

Example Code:

// Before
sessionResolver.resolveSession();

// After
const channel = getChannelFromCLI();
const replyAccount = getReplyAccountFromCLI();
sessionResolver.resolveSession(channel, replyAccount);

Verification

To verify that the fix worked, check the following:

  • The session resolver receives the necessary context.
  • The lookup by delivery context works correctly.
  • The sessions are resolved to the correct channel/thread.

Extra Tips

  • To prevent regression, consider updating the source code to include the necessary parameters and recompiling the dist/register.agent-DHoJWl4M.js file.
  • Make sure to test the fix thoroughly to ensure it works as expected in different scenarios.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#installation#tensor shape#autograd error#latency issue#model loading#dependency error#configuration error#environment variable

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING