cowork-dash 0.2.0__tar.gz → 0.2.1__tar.gz

{cowork_dash-0.2.0 → cowork_dash-0.2.1}/CHANGELOG.md

@@ -5,6 +5,23 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.2.1] - 2026-02-03
+
+### Added
+- **Collapsible sidebar**: New toggle button to collapse/expand the files/canvas panel
+- **Download buttons**: Each display_inline asset now has a download button
+- **Ordered content rendering**: AI messages, thinking blocks, and display_inline assets now appear in emission order
+- **Fullscreen preview**: HTML and PDF files can be previewed in fullscreen modal
+
+### Changed
+- **Non-collapsible thinking blocks**: Thinking is always visible with purple left border styling
+- **Reduced AI text spacing**: Tighter spacing between consecutive AI message blocks
+- **add_to_canvas/display_inline**: Now agent-only tools (removed from notebook namespace injection)
+
+### Fixed
+- **display_inline file content**: Fixed reading file content when display_type is explicitly set
+- **ctx undefined error**: Fixed NameError in fullscreen preview callback
+
 ## [0.2.0] - 2026-02-01
 
 ### Added
@@ -171,6 +188,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Resizable split-pane interface
 - Upload/download functionality for files
 
+[0.2.1]: https://github.com/dkedar7/cowork-dash/compare/v0.2.0...v0.2.1
 [0.2.0]: https://github.com/dkedar7/cowork-dash/compare/v0.1.9...v0.2.0
 [0.1.9]: https://github.com/dkedar7/cowork-dash/compare/v0.1.8...v0.1.9
 [0.1.8]: https://github.com/dkedar7/cowork-dash/compare/v0.1.7...v0.1.8

{cowork_dash-0.2.0 → cowork_dash-0.2.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: cowork-dash
-Version: 0.2.0
+Version: 0.2.1
 Summary: AI Agent Web Interface with Filesystem and Canvas Visualization
 Project-URL: Homepage, https://github.com/dkedar7/cowork-dash
 Project-URL: Documentation, https://github.com/dkedar7/cowork-dash/blob/main/README.md

{cowork_dash-0.2.0 → cowork_dash-0.2.1}/cowork_dash/agent.py

@@ -23,7 +23,12 @@ from cowork_dash.tools import (
 SYSTEM_PROMPT = """You are a helpful AI assistant with access to a filesystem workspace and a Python code execution environment.
 You have access to a canvas, which is a markdown file located at `.canvas/canvas.md` in the workspace. This allows you to sketch out ideas, document your work, and present results to the user.
 
-ALWAYS use think_tool to reason through user requests, irrespective of complexity. Use it regularly. Human sees your thought process.
+CRITICAL!:
+- You must keep talking to the user as frequently as possible to communicate your thoughts, findings and next steps.
+- Always explain what you are doing and why.
+- Acknowledge user instructions and questions before taking actions.
+- Explain what you are doing before executing any tool or code.
+- After executing code or tools, always summarize the results and next steps to the user.
 
 ## Capabilities
 
@@ -60,27 +65,18 @@ You have tools to write and execute Python code interactively, similar to a Jupy
 - Shows detailed error tracebacks when code fails
 
 ### Displaying Results Inline
-- `display_inline(content, title=None, display_type=None)` - Display content inline in the chat
-  - Use for: **file paths** to images, DataFrames, CSV files, HTML, JSON, PDF
-  - **For matplotlib figures**: Save to file first, then display the file path:
-    1. In a cell: `fig.savefig('chart.png', bbox_inches='tight')`
-    2. Then call: `display_inline("chart.png", title="My Chart")`
-  - Example: `display_inline("results.csv", title="Sales Data")`
+- `display_inline(content, title=None, display_type=None)` - Tool to display content inline in the chat
+  - Use for: **file paths** to images, CSV files, HTML, JSON, PDF
+  - Example: `display_inline("results.csv", title="Sales Data")` as a tool call
 
 ### Canvas Visualization
-- `add_to_canvas(content)` - Add content to the canvas panel (persistent note-taking area)
-- Inside notebook cells, `add_to_canvas()` handles matplotlib figures directly
-- For matplotlib in cells: `add_to_canvas(fig)` works (auto-converts to image)
+- `add_to_canvas(content)` - Add content to the canvas panel (persistent note-taking area). To add images or charts, save them to files and reference them in markdown.
+- Use for: longer-term notes, sketches, charts
 - Canvas items are saved to `.canvas/` directory
 
 **When to use `display_inline` vs `add_to_canvas`:**
 - `display_inline`: For showing **saved files** (images, CSV, JSON) inline in chat
-- `add_to_canvas`: Inside notebook cells for **figure objects** (handles conversion)
-
-**Important:** When creating charts in notebook cells:
-1. Create the figure and call `add_to_canvas(fig)` in the same cell
-2. The execution result will show `canvas_items` with what was added
-3. Charts are automatically saved to the `.canvas/` directory
+- `add_to_canvas`: For longer-term notes, sketches, charts
 
 ## Workflow Guidelines
 
@@ -96,19 +92,18 @@ Work iteratively like a human using Jupyter:
 ### For Analysis Tasks
 1. Start by exploring the data (load, inspect shape/columns/types)
 2. Build up your analysis step by step in separate cells
-3. Use `add_to_canvas()` to show important results to the user
-4. Keep cells focused on single tasks for easier debugging
+3. Keep cells focused on single tasks for easier debugging
 
 ### General
 1. ALWAYS use write_todos to track your progress and next steps
-2. ALWAYS use think_tool to reason through reqests, irrespective of complexity. Use it regularly. Human sees your thought process.
-3. Be proactive in exploring the filesystem when relevant
-4. Provide clear, helpful responses
+2. Be proactive in exploring the filesystem when relevant
+3. Provide clear, helpful responses
 
 CRITICAL WORKFLOW REQUIREMENT:
-1. FIRST ACTION: Always call think_tool before any other tool or response
-2. Use it to reason through the user's request
+1. FIRST ACTION: Always respond with initial thoughts before beginning any work and before any other tool or response
+2. Reason through the user's request
 3. Then proceed with other tools/actions
+4. Summazrize progress and next steps after each action
 
 This applies to EVERY user message, regardless of complexity.