You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Read a media value's content with ['base64'] - #5608
A query describes an image, audio, PDF or video value without its content, as {"$media", "mime", "base64_len"}, so a result of a thousand runs is not a thousand pictures. A path that ends in ['base64'] on a media value now reads that one value's content as base64 text, from the value's own blob or from the child blob a large content lives in. Media that names a URL or a file holds no content and reads as missing.
Studio uses this path to show images and PDFs in span details (BoundaryML/bcs#263).
Medium Risk
Changes captured-value navigation and SQL query semantics for media; behavior is well-tested but touches telemetry/query paths that Studio depends on.
Overview baml query can now load a single media value’s payload while default rendering still shows only lightweight descriptors ($media, mime, base64_len or url).
Value navigation treats base64 as a special key on media objects: paths like input_args['small']['_data']['base64'] return the stored base64 text (inline or from an external CAS child blob), respect blob budgets, and yield missing for URL/file-backed media or other keys such as mime. Documentation for baml query describes this behavior.
Coverage adds unit tests in btel_reader and an end-to-end query test that asserts small/large images, URL-only media, descriptors, and SQL equality on the loaded content.
Reviewed by Cursor Bugbot for commit e64fa2e. Bugbot is set up for automated code reviews on this repo. Configure here.
Summary by CodeRabbit
New Features
Querying a media value’s base64 content now returns its text for inline and separately stored image, audio, PDF, and video data. URL-backed media and unsupported media keys continue to return no value.
Media descriptors remain content-free; paths that end at base64 can read the content, while paths beneath it do not resolve.
Documentation
Clarified how media content is represented and accessed in queries.
No actionable comments were generated in the recent review.
Walkthrough
Media values can now expose their content through the MEDIA_CONTENT navigation key. Inline payloads are returned directly; referenced payloads are loaded and validated. Tests cover missing paths, unavailable content, and query behavior.
Changes: Media Content Navigation
Layer / File(s)
Summary
Resolve media content baml_language/crates/btel_reader/src/value.rs, baml_language/crates/btel_reader/src/value/span.rs, baml_language/crates/btel_reader/src/value/span/tests.rs, baml_language/crates/baml_query_btel/tests/values.rs, baml_language/crates/baml_builtins2/keyword_docs/baml_keywords.yaml
The MEDIA_CONTENT key resolves inline content or loads and validates content from a referenced child blob. Tests cover supported and missing paths, unavailable content, descriptor rendering, and query filtering. Query documentation describes media content access.
sequenceDiagram
participant BtelQuery
participant ValueStep as value::step
participant MediaText as span::media_text
participant ChildBlob
BtelQuery->>ValueStep: Navigate to MEDIA_CONTENT
ValueStep->>MediaText: Resolve media payload
opt External payload
MediaText->>ChildBlob: Load referenced content
ChildBlob-->>MediaText: Return child content
end
MediaText-->>ValueStep: Return content or navigation result
ValueStep-->>BtelQuery: Return navigation result
Loading
Suggested reviewers:2kai2kai2, hellovai
Merge Risk: Minimal · up to 65875
This change lets queries read a media value's content as base64 text. Its behavior is covered by unit and query tests, and no merge-blocking risk was identified.
Security architecture risk: Low · up to 65875
Explicit queries can now return captured media content. Existing redaction, integrity checks, and read budgets remain in place, and no boundary bypass was identified. Access controls in the consuming application were not available for verification.
Retained concerns
No architecture-level concerns identified.
Security review details
Security Blast Radius
inferred — At the inspected query layer, the exposure expands to captured media reachable through value navigation in the configured project's CAS. The change does not itself introduce a new network destination, arbitrary media-file read, or additional service credential. Remote consumer authorization and tenant isolation remain outside the inspected scope.
Trust Boundaries and Controls
observed — User-selected query paths reach the new payload read through the existing read-only query machinery. The SQL translator accepts only one query statement, and SQLite authorization denies non-read actions and privileged file or extension functions. These controls constrain execution authority but do not establish who may access a project's captured payloads.
Resilience and Maintainability Implications
observed — The existing string-scalar path returns complete text rather than applying the structured-render text cap. The new media path inherits this behavior. Default CAS reads are capped at 64 MiB, and default query output and duration budgets remain enabled; however, output size is checked after collecting a row, so that budget is not a strict peak-memory ceiling.
Pre-merge checks: 4
Check name
Status
Explanation
Title check
The title "Read a media value's content with ['base64']" matches the main change. The PR adds a query path ending in ['base64'] that reads media payloads as base64 text, including content in child CAS…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Description Check
Check skipped - CodeRabbit’s high-level summary is enabled.
Full details: Title check
Explanation
The title "Read a media value's content with ['base64']" matches the main change. The PR adds a query path ending in ['base64'] that reads media payloads as base64 text, including content in child CAS blobs. The raw summary confirms the same behavior in the query docs, the btel_reader span navigation, and the new tests. The title is short, specific, and does not list files.
Finishing Touches
Generate unit tests (beta)
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
A rabbit finds a path to text, Through blobs it hops, then checks what’s next. Inline strings come into view, Missing paths stay missing too. The query nibbles base64 greens.
Recent review info
Run configuration
Source mode: Auto
Repository: Unavailable
Branch: Unavailable
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Repository UI
Review profile: CHILL
Plan: Advanced
Run ID: 688851ce-c73d-4928-951b-77eed2b3282e
Commits
Reviewing files that changed from the base of the PR and between 43e1232 and 65875ee.
Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 2 remain after this review.
⚠️ Please fix the size gate issues or acknowledge them by updating baselines.
Artifact
Platform
File
Gzip
Gated on
Baseline
Delta
Status
✅
baml-cli
Linux
🔒 65.0 MB
27.6 MB
file
73.1 MB
-8.1 MB (-11.0%)
OK
❌
packed-program
Linux
🔒 39.3 MB
16.2 MB
file
29.2 MB
+10.2 MB (+34.9%)
FAIL
❌
bridge_wasm
WASM
26.1 MB
🔒 7.7 MB
gzip
5.7 MB
+2.1 MB (+36.5%)
FAIL
🔒 = the size this artifact is GATED on (ceiling + delta). Binaries gate on file size (installed binary); WASM gates on gzip (download size). The other size is shown for information only.
Details & how to fix
Violations:
packed-program (Linux) file_bytes: 39.3 MB exceeds limit of 30.1 MB (exceeded by +9.2 MB, policy: max_file_bytes)
packed-program (Linux) file_delta_pct: +34.9% exceeds limit of 3.0% (exceeded by +31.9pp, policy: max_delta_pct)
bridge_wasm (WASM) gzip_bytes: 7.7 MB exceeds limit of 5.9 MB (exceeded by +1.9 MB, policy: max_gzip_bytes)
bridge_wasm (WASM) gzip_delta_pct: +36.5% exceeds limit of 3.0% (exceeded by +33.5pp, policy: max_delta_pct)
A query describes an image, audio, PDF or video value without its content,
as `{"$media", "mime", "base64_len"}`, so a row of a thousand runs is not
a thousand pictures. A path that ends in `['base64']` on a media value now
reads that one value's content as base64 text, from the value's own blob
or from the child blob a large content lives in. Media that names a URL
or a file holds no content and reads as missing.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
A query describes an image, audio, PDF or video value without its content, as
{"$media", "mime", "base64_len"}, so a result of a thousand runs is not a thousand pictures. A path that ends in['base64']on a media value now reads that one value's content as base64 text, from the value's own blob or from the child blob a large content lives in. Media that names a URL or a file holds no content and reads as missing.Studio uses this path to show images and PDFs in span details (BoundaryML/bcs#263).
Part of a stack; review the PRs in order.
🤖 Generated with Claude Code
Note
Medium Risk
Changes captured-value navigation and SQL query semantics for media; behavior is well-tested but touches telemetry/query paths that Studio depends on.
Overview
baml querycan now load a single media value’s payload while default rendering still shows only lightweight descriptors ($media,mime,base64_lenorurl).Value navigation treats
base64as a special key on media objects: paths likeinput_args['small']['_data']['base64']return the stored base64 text (inline or from an external CAS child blob), respect blob budgets, and yield missing for URL/file-backed media or other keys such asmime. Documentation forbaml querydescribes this behavior.Coverage adds unit tests in
btel_readerand an end-to-end query test that asserts small/large images, URL-only media, descriptors, and SQL equality on the loaded content.Reviewed by Cursor Bugbot for commit e64fa2e. Bugbot is set up for automated code reviews on this repo. Configure here.
Summary by CodeRabbit
base64content now returns its text for inline and separately stored image, audio, PDF, and video data. URL-backed media and unsupported media keys continue to return no value.base64can read the content, while paths beneath it do not resolve.