Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
freem
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Openai/694057b6-101c-8007-9a65-c40578c7252d
(section)
Add languages
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
===== Tool calls may appear: ===== * in structured fields (preferred), or * in assistant content in fallback mode. The worker must support both. ====== When an assistant message contains tool_calls, parse them into a list of tool call objects, then partition: ====== * normal_calls = [c for c in tool_calls if c.name in normal_tool_names] * exit_calls = [c for c in tool_calls if c.name in exit_tool_names] * unknown_calls = everything else Rules: * If unknown_calls is non-empty → treat as FAILED(reason="tool_parse_error") (preserve partial output). * Record each exit_call into signals[] immediately (best effort parsing). * Proceed with normal_calls via the normal tool loop. Important detail (prevents “unanswered tool calls”): * When continuing generation after normal tool execution, the worker should append an assistant message containing only the normal tool calls, not the exit tool calls. * Exit tool calls are treated as out-of-band signals and are not part of the conversation that requires tool responses. This keeps exit-tools “no round trip” while avoiding confusing the model with unresponded calls. ====== If no structured tool_calls are present but the model is expected to call tools, the worker uses a BIOS-enforced convention, for example: ====== * A tool call is represented as a single JSON object (or JSON line) that includes: - {"tool": "<name>", "arguments": { ... }} - optionally with a stable prefix/suffix marker if you choose to enforce one. Fallback parsing rules: * Attempt parsing only when the accumulated assistant output contains a clearly delimited tool-call candidate. * If parsed tool name is in normal tools: - treat it as a normal tool call - strip the tool-call directive from the user-visible output (so the final result isn’t polluted) * If tool name is in exit tools: - record signal - optionally strip directive from output (recommended) * If parsing fails or tool name unknown: - FAILED(reason="tool_parse_error") (preserve output as-is for debugging) This fallback logic should be isolated in tooling.py and unit-tested heavily.
Summary:
Please note that all contributions to freem are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 (see
Freem:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)