Skip to content

fix(engine): bound the relayfile record stored in message metadata - #702

Merged
agent-relay-code[bot] merged 2 commits into
mainfrom
batch/20261120-0902
Nov 20, 2026
Merged

agent-relay-code[bot] merged 2 commits into
mainfrom
batch/20261120-0902

Conversation

@agent-relay-code

@agent-relay-code agent-relay-code Bot commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

Hourly batch from the relaycast agent host: batch/20261120-0902 on origin/main, one merge commit per branch below.

Changes

origin/agent/relayfile-record-cap

  • bb49118 fix(engine): bound the relayfile record stored in message metadata
    The relayfile inbound bridge stored the whole parsed provider record (up to
    the 1 MiB body limit) in messages.metadata, and that metadata is copied again
    into the webhook outbox and stream events. Nothing bounded it.
    A record whose JSON is over 8 KiB (UTF-8; engine config
    relayfileRecordMetadataMaxBytes) is now stored as record: null plus
    record_omitted { reason, bytes, limit }. Path, revision and the rest of the
    metadata stay, so consumers can fetch the record from relayfile. Message
    text and the idempotency fingerprint are unchanged.

    Co-Authored-By: Claude noreply@anthropic.com

Diff vs origin/main: 7 files changed, 222 insertions(+), 4 deletions(-)
Paths: CHANGELOG.md, docs/repository-guide.md, openapi.yaml, packages/engine/

Verification

  • Review round 1: SIGNOFF (cost $2.3198, batch total $2.3198)
  • SIGNOFF. The batch deploys only relaycast-cloud; nothing to deploy for this repo.

Gating

Draft on purpose. Merging, npm releases and production deploys need a human (Khaliq's direct OK). The batch only deploys to this host's stage (dev), and only after a reviewer SIGNOFF.


Autofix with [code]smith
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.

Relaycast Agent Host and others added 2 commits November 20, 2026 08:14
The relayfile inbound bridge stored the whole parsed provider record (up to
the 1 MiB body limit) in messages.metadata, and that metadata is copied again
into the webhook outbox and stream events. Nothing bounded it.
A record whose JSON is over 8 KiB (UTF-8; engine config
relayfileRecordMetadataMaxBytes) is now stored as record: null plus
record_omitted { reason, bytes, limit }. Path, revision and the rest of the
metadata stay, so consumers can fetch the record from relayfile. Message
text and the idempotency fingerprint are unchanged.

Co-Authored-By: Claude <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Nov 20, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 0a9ac880-6b3c-4f5e-aeb9-5b153c3f3dde

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@agent-relay-code

Copy link
Copy Markdown
Contributor Author

Review round 1: SIGNOFF (cost $2.3198, batch total $2.3198)

@agent-relay-code

Copy link
Copy Markdown
Contributor Author

SIGNOFF. The batch deploys only relaycast-cloud; nothing to deploy for this repo.

@agent-relay-code
agent-relay-code Bot marked this pull request as ready for review November 20, 2026 09:33
@agent-relay-code agent-relay-code Bot changed the title batch: agent changes 20261120-0902 fix(engine): bound the relayfile record stored in message metadata Nov 20, 2026

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Devin Review

@greptile-apps

greptile-apps Bot commented Nov 20, 2026 •

Copy link
Copy Markdown

RetriggerView in GreptileConfidence Score: 5/5

[Medium impact] The code appears safe to merge once the required human approval is given.

Summary

This PR caps the provider record saved in Relayfile message metadata at 8 KiB by default.

  • Relayfile messages keep oversized provider records out of their metadata.

No actionable issues were found. Tests were reviewed but not run.

agent-relay-code[bot] explicitly states that the draft is intentional pending human approval.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A[Authenticated Relayfile event] --> B[Parse provider record]
  B --> C[Format message text]
  B --> D{Record JSON within byte limit?}
  D -->|Yes| E[Keep record]
  D -->|No| F[Null record and omission details]
  E --> G[Message metadata]
  F --> G
  C --> H[Save message]
  G --> H
  H --> I[Webhook and stream events]
Loading

Reviews (1) · Last reviewed commit: "Merge remote-tracking branch 'origin/age..." · Reviewed by Greptile

@agent-relay-code
agent-relay-code Bot merged commit cbd099a into main Nov 20, 2026
19 checks passed
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.

0 participants