Skip to content

Disallow use of sqlite sessions, but pass through others #993

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jul 24, 2025

Conversation

tconley1428
Copy link
Contributor

What was changed

Why?

Checklist

  1. Closes

  2. How was this tested:

  1. Any docs updates needed?

@tconley1428 tconley1428 requested a review from a team as a code owner July 24, 2025 17:47
Copy link
Contributor

@dandavison dandavison left a comment

Choose a reason for hiding this comment

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

LGTM. So we fail the task, since it's something they can fix in their code. And we know they're in workflow code because we check that at the top of our Runner.run. Will it make sense at some point for our plugin to give them a custom workflow-compatible in-memory session that they can use?

@tconley1428
Copy link
Contributor Author

There's definitely a possibility for our plugin to provide session implementations. Whether we do that via memory, large payload, or something else is still pending. Sessions were only added to the agents SDK a few weeks ago, so it isn't in plan yet.

@tconley1428 tconley1428 merged commit 3d9bfee into main Jul 24, 2025
27 of 28 checks passed
@tconley1428 tconley1428 deleted the openai/block_sqlite_session branch July 24, 2025 23:18
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