-
Notifications
You must be signed in to change notification settings - Fork 564
Description
Pre-submit Checks
- I have searched Warp bugs and there are no duplicates
- I have searched Warp known issues page and my issue is not there
- I have an issue with AI and have included the debugging ID (Optional, but helps expedite the AI quality fix). Debugging ID instructions
- I have technical issue and have included the logs (optional, but helps expedite the bug fix). Log instructions
Describe the bug
Raw content from the agents is processed / displayed as regular JSON? in the display and not executed as commands where appropriate
To reproduce
Very difficult to reproduce as it just happens "randomly" - although once in the new 'mode' restarting doesn't fix it. I can tell you that I am using the Lite Model (as out of credits). Tried downgrading to an earlier version a this initially fixed the problem, but then after 30 mins or so of use it reverted to just displaying the underlying conversation rather than actioning it (where appropriate). See example output below.
Expected behavior
Program should work as normal and respond to the outputs from the models/agents instead of just displaying the text.
Screenshots, videos, and logs
Example of what is seen in the window:
Let me analyze the parquet extension's entry points to create our extension header:
role: assistant
called function: name=create_file, id=toolu_01G4q8Jdg8uIGVmF6TDIvaSE
with arguments: {"summary":"Creating new DuckDB extension header based on parquet example","file_path":"/Users/mjboothaus/code/github/databooth/duckdb-ext-apple-health/src/include/apple_health_extension.hpp","contents":"//===----------------------------------------------------------------------===//\n// DuckDB\n//\n// apple_health_extension.hpp\n//\n//\n//===----------------------------------------------------------------------===//\n\n#pragma once\n\n#include "duckdb.hpp"\n\nnamespace duckdb {\n\nclass AppleHealthExtension : public Extension {\npublic:\n void Load(DuckDB &db) override;\n std::string Name() override;\n std::string Version() const override;\n};\n\n// Workouts function state\nstruct WorkoutsFunctionState : public GlobalTableFunctionState {\n idx_t rows_loaded = 0;\n\n static unique_ptr Init(ClientContext &context, TableFunctionInitInput &input);\n};\n\n// Workouts function data\nstruct WorkoutsFunctionData : public TableFunctionData {\n string filename;\n\n explicit WorkoutsFunctionData(string filename_p) : filename(std::move(filename_p)) {}\n};\n\n} // namespace duckdb"}
role: user
function call name=create_file (id=toolu_01G4q8Jdg8uIGVmF6TDIvaSE) returned output:
{"file_content_after_create":{"path":"/Users/mjboothaus/code/github/databooth/duckdb-ext-apple-health/src/include/apple_health_extension.hpp","content":"1|//===----------------------------------------------------------------------===//\n2|// DuckDB\n3|//\n4|// apple_health_extension.hpp\n5|//\n6|//\n7|//===----------------------------------------------------------------------===//\n8|\n9|#pragma once\n10|\n11|#include "duckdb.hpp"\n12|\n13|namespace duckdb {\n14|\n15|class AppleHealthExtension : public Extension {\n16|public:\n17| void Load(DuckDB &db) override;\n18| std::string Name() override;\n19| std::string Version() const override;\n20|};\n21|\n22|// Workouts function state\n23|struct WorkoutsFunctionState : public GlobalTableFunctionState {\n24| idx_t rows_loaded = 0;\n25|\n26| static unique_ptr Init(ClientContext &context, TableFunctionInitInput &input);\n27|};\n28|\n29|// Workouts function data\n30|struct WorkoutsFunctionData : public TableFunctionData {\n31| string filename;\n32|\n33| explicit WorkoutsFunctionData(string filename_p) : filename(std::move(filename_p)) {}\n34|};\n35|\n36|} // namespace duckdb","line_range_start":1,"line_range_end":36}}
Operating system (OS)
macOS
Operating system and version
15.7.1 (24G231)
Shell Version
zsh 5.9 (arm64-apple-darwin24.0)
Current Warp version
No response
Regression
Yes, this bug started recently or with an X Warp version
Recent working Warp date
Hard to say - I went back to 1 October version and it appeared there too - first noticed in 8 October version.
Additional context
No response
Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
Is this an issue only in Warp?
Yes, I confirmed that this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
Ignore