Skip to content

feat: add structured output and history processors - #1

Merged
DEENUU1 merged 1 commit into
mainfrom
feat/summary-and-response
Nov 29, 2025
Merged

feat: add structured output and history processors#1
DEENUU1 merged 1 commit into
mainfrom
feat/summary-and-response

Conversation

@DEENUU1

@DEENUU1 DEENUU1 commented Nov 29, 2025

Copy link
Copy Markdown
Member

Summary

Add structured output and history processors features, enabling type-safe responses with Pydantic models and automatic conversation summarization for managing token limits in long sessions.

@DEENUU1
DEENUU1 merged commit 3d88924 into main Nov 29, 2025
7 of 8 checks passed
@DEENUU1
DEENUU1 deleted the feat/summary-and-response branch November 29, 2025 22:40
DEENUU1 added a commit that referenced this pull request Jun 26, 2026
Attaching a file gave no feedback beyond a toast. Now:

- A chip bar above the prompt shows pending attachments as `[Image #1]`,
  `[chart.png]`, … so a Ctrl+V paste is visible, not just a notification.
  Esc on an idle prompt clears them.
- Dropping a file onto the terminal (a bracketed paste of its path) is
  intercepted: an image attaches as a chip; any other file is dropped in as an
  `@path` reference the prompt expansion picks up on submit. Paths that aren't
  real files fall through to normal text paste.

Labels are markup-escaped so a bracketed `[Image #1]` isn't parsed as a
content-markup tag (which rendered as a stray box glyph).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
DEENUU1 added a commit that referenced this pull request Jun 26, 2026
The attachment badge was built as `[dim]🖼 1 image attached[/dim]` and folded
into the user message text — but UserMessage escapes brackets, so the markup
showed literally and the emoji looked off. Match Claude Code: pass attachment
labels to UserMessage separately and render each as a dim `└ [Image #1]`
sub-line under the message (brackets escaped, markup applied).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant