Error: e.content.some is not a function

[afganhalbana]

Summary

out of sudden commandcode is crashing and can't continue to process any command. Even invoking skills is also not working.
Trace ID:

• 7764fd354468682053b5c8c1e2b897ea
• a42675f8471595fe39a95db58e890fe0
• 7489cc5242a5e0cb7a99ee99e6418fbc
• e11cf3fae37bec44c17cd786512cd0e6

it's solved after i did /clear but i lost all the previous context.

Expected Behavior

can process the command and showing meaningful error message.

Actual Behavior

stuck can't process any command.

Steps to reproduce the issue

not sure how to do it but the last command that i

Command Code Version

v1.28.4

Operating System

macOS

Terminal/IDE

iterm with herdr

Shell

No response

Session file (optional)

when i get back to the corrupt session state, i see this alert
Failed to load session: Failed to load session: e.filter is not a function. Starting fresh session.
⚠ Failed to load session: e.filter is not a function. Starting fresh session.

and when i tried to run /export jsonl got this error Nothing to export yet — the transcript is created on the first message.

Fix prompt (optional)

No response

Additional context

No response

[ahmadawais]

Checking.

[ahmadawais]

Root cause (traced via Axiom)

All four trace IDs point to the same crash, in the agent loop's send path:

TypeError: e.content.some is not a function
    at hoistToolResultImages
    at prepareForSend
    at agentLoop

prepareForSend is the wire-validity pass run before every model call. Its last step, hoistToolResultImages, scans user messages for tool_result blocks and calls block.content.some(...) to detect nested images. Anthropic's wire format allows tool_result.content to be a string OR a block array. Our internal shape always uses the array, but a string can enter from a stored/imported session (the v3 session format keeps AgentMessage verbatim on disk, no normalization on load) or a mod/hook-written message.

When that happens, .some on a string throws — the turn dies with run_error, and since the bad message stays in the session, every later command crashes too until /clear discards it. That matches the report: /clear "fixed" it at the cost of the whole conversation.

The same string-vs-array shape is also what produced the e.filter is not a function alert on the corrupt session load path.

Fix

PR https://github.com/CommandCodeAI/commandcode/pull/3945:

• prepareForSend gains a normalization Step 0: string (or malformed non-array) tool_result.content is folded into the canonical [{type:'text', text}] array before any other step runs, so no downstream .some/.filter/.map can hit a string.
• hoistToolResultImages is hardened with Array.isArray(block.content) guards as defense-in-depth.

Regression tests cover both the string and malformed non-array cases; full harness core/session/model suite passes (736 tests), typecheck and biome clean.

[ahmadawais]

@ahmadbilaldev can you check this please?

[afganhalbana]

recently happening again at my end

QUESTION  [User answered questions]
 └ Given you declined to narrow the rule, how should I proceed? → Risk broader sweep, revert later

⠶ OK, broader sweep. Let me scan for candidates first, then propose the diff before applying.

⚠ Error: e.content.some is not a function

  Type "continue" to try again. If the issue persists, contact support: https://commandcode.ai/discord
  Trace ID: 45e80923a5557ab391bfb4e25d8cdcd2

reproducable if i'm invoking /grill-with-docs skills

seems i've found the issue, last log is trying to execute this command

rtk ast-grep run --pattern '//' --lang kotlin --json 2>/dev/null | head -3 ; rtk ast-grep run --lang kotlin --pattern '\$\$'
       2>/dev/null | head -1 ; true]
 │ [
 │ {
 │   "text": "//",
 └

meanwhile this is not the right command if i run this manually on terminal it shows:
Parsed the pattern but it matched nothing in this run. Try using playground to refine the pattern.
See also: https://ast-grep.github.io/playground.html

rtk ast-grep is not a real command — ast-grep is a separate tool, not an rtk subcommand. mixing them broke execution.

[ahmadbilaldev]

Taking a look, thanks for reporting.