Rick Hennigan
Rick Hennigan
Clicking the insert hover button for this "1+1" writes it into the chat output cell instead of creating a new cell:
Incomplete tool calls are formatted with the label "Using **Tool Name**" since that usually means that the LLM is still writing out the tool call. However, if chat is stopped,...
Pressing the `\` key while editing inline cells yields an internal failure due to the inline WL template event handler firing: This interferes with the ability to type special characters,...
It would be nice if the `Import["attachment://content-096bb48ec62ac413"]` did something reasonable in the example below:
Since `CellTrayWidgets` is not supported in cloud, these buttons will need an alternate implementation when using cloud notebooks:
The submenu will be displayed as an unevaluated symbol and an error will print to the messages menu: Debug Data | Property | Value | | --- | --- |...
Since not all users have a GitHub account, this would allow submitting error reports to a Wolfram Cloud API which would then create the relevant issue on the user's behalf.
This could be something like ``$InternalFailureData`` and would contain the same type of information generated here: https://github.com/WolframResearch/Chatbook/blob/dd0fefc0966dd6b49e32a27d61dc39679cfa20be/Source/Chatbook/Common.wl#L580-L591 However, it should not do any of the markdown formatting or truncation that's...
Tool outputs should be sanitized so they don't include tokens like `ENDTOOLCALL`: