Klavis Sandbox on Fireworks EP #388
Merged
+343
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note
Integrates Klavis sandbox lifecycle into EP pytest utilities and provides a working Gmail sandbox eval.
KlavisSandboxRolloutProcessormanages full sandbox flow: create/init (initialize_*_sandbox), generate temp MCP config, runAgent, export/dump sandbox state, attach results torow.execution_metadata.extra, cleanup and delete sandboxKlavisSandboxRolloutProcessorviaeval_protocol.pytest.__init__klavisdependency group (klavis>=2.18.0) and lockfile updatestest_pytest_klavis_sandbox.pyand datasetklavis_gmail_sandbox_test.jsonl: adapts JSONL to EP rows, runs againstserver_name="gmail", and scores via Fireworks LLM by comparing dumped sandbox state to providedground_truthWritten by Cursor Bugbot for commit 7f35e24. This will update automatically on new commits. Configure here.
See our slack channel for demo