base64 handling not using `ToolFile`

[baggiiiie]

issues and observation

I have observed that, when an API returned file content as base64 inside a json blob, agents tried to decode it with atob, TextDecoder and other methods that's not made available in the quickjs.

and because of this, agents then tried to handwrite a decoder inside quickjs, completely ignoring the emit() and ToolFile related instructions in the skill.

potential fixes

• update the skill to instruct agents to also wrap base64 data from json responses in a ToolFile and call emit().

other info

• executor version: 1.5.36
• model/harnees used: opus 4.8/5 in cursor, 5.6 sol in pi with my own pi-executor adapter
• connected to github with its openAPI spec
• repro prompt:

use `executor` to fetch a text file from any GitHub repo you have access to via `repos.getContent`, show content

stop and report if there's any error during the executor call and show me the code u wrote

[baggiiiie]

on a relevant note , im discovering that, emit() content are actually visible to the agent. and if emit() and return are both called, returned object is dropped, despite in the skill it says:

executor/packages/core/execution/src/skills.ts

Line 49 in 541549a

"- Use `emit(value)` to append user-visible output and return `undefined`. Plain values become MCP text content. MCP content blocks are forwarded as-is. `ToolFile` values are rendered by MIME. Emitted output goes to the user, not back to you; the result envelope reports an `emitted` count so you can confirm it landed, but to read a value yourself, `return` it.",

this is actually not the behavior of emit(). in cursor

same prompt running in pi