Skip to content

Optional response model for Rank#4

Merged
rgambee merged 5 commits intomainfrom
rank-response-model
Jan 15, 2026
Merged

Optional response model for Rank#4
rgambee merged 5 commits intomainfrom
rank-response-model

Conversation

@rgambee
Copy link
Copy Markdown
Member

@rgambee rgambee commented Jan 15, 2026

This lets you specify the response model for Rank in case you want multiple output columns. It's optional so you can still specify only a column name.

I also updated the rank examples to have better agent tasks. The task should describe how to score a single row. I admit this could be clearer and would like to document it better.

@rgambee rgambee requested a review from jackwildman January 15, 2026 17:49
Copy link
Copy Markdown
Contributor

@jackwildman jackwildman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good

@rgambee rgambee merged commit b384ca9 into main Jan 15, 2026
1 check passed
@rgambee rgambee deleted the rank-response-model branch January 15, 2026 18:44
hnykda pushed a commit that referenced this pull request Jan 22, 2026
Users can now specify the response model for Rank
in case they want multiple output columns. It's
optional, so they can still specify only a column
name.
RafaelPo added a commit that referenced this pull request Feb 24, 2026
- Add defense-in-depth expiration check on auth codes after deserialization
- Derive revocation TTL from token remaining lifetime + 60s buffer
- Remove exc_info=True from JWT failure debug log to avoid leaking internals
- Tighten SameSite cookie policy from lax to strict on auth state cookies
- Validate Supabase token response via Pydantic model_validate with clear error
- Add tests for expired auth codes, revocation TTL, and malformed Supabase responses

Co-Authored-By: Claude Opus 4.6 <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.

2 participants