Skip to content

feat(frontend): pick event fields for an event automation's instruction - #7913

Merged
mmabrouk merged 13 commits into
release/v0.127.2from
feat/automation-event-field-picker
Oct 29, 2026
Merged

mmabrouk merged 13 commits into
release/v0.127.2from
feat/automation-event-field-picker

Conversation

@mmabrouk

Copy link
Copy Markdown
Member

Context

A user who makes an event automation ("when a pull request opens in GitHub, review it") cannot see or use what is in the event. The Instruction box on /m is a plain text box, so the stored instruction is static text. The agent never gets the pull request, the email or the message that started the run. The old field picker was deleted with the old subscription form in 89c2d80c39.

The backend PR under this one (#7911) adds the full event to the agent's message by default (data.include_event) and records the event on each delivery (data.event). This PR is the screen for it.

Changes

For event automations only, the Instruction field now has four parts. Schedules keep today's plain composer.

  1. Pills in the instruction. The text box is a small rich editor. An event field shows as a chip (a "pill") with its label and an x. Backspace or the x removes it like one character.
  2. Field cards. Under the box, one card per field of the event's payload schema, which the catalog already returns from Composio. Each card shows a humanized name (createdBy reads "Created by") and Composio's own description. A click adds the field as a pill. A card whose field is already in the instruction shows a check.
  3. Include-event checkbox. "Also attach the full event, so the agent can use any detail". It reads data.include_event. An automation saved before this change has no key, so it reads as checked.
  4. "What the agent gets" preview. The exact text the agent gets. Pills take their values from the newest delivery that recorded an event. With no such delivery, each pill shows as its label in square brackets, for example [Title].

How a pill is stored. A pill is a text part whose text is a selector into the event: $.event.attributes.<key>. The dispatcher already replaces a selector with its value. For "Review " and the Title pill, the stored mapping is:

{"messages": [{"role": "user", "content": [
  {"type": "text", "text": "Review "},
  {"type": "text", "text": "$.event.attributes.title"}
]}]}

A key with characters other than letters, digits and underscores uses the bracket form, $.event.attributes["a.b"]. A pill is always a text part, even when it is alone, so a field that holds a list stays text.

Run now sends the preview text. When the user presses it, the screen fetches the deliveries once, takes the newest recorded event, and builds the text with the same function the preview uses. If that fetch fails, no run starts, the error goes to the console, and the button stays usable. A mapping the composer cannot show (several messages, a non-user message) keeps today's warning and today's Run now text.

Other mapping keys are kept. Reading and writing the instruction now changes only the message key. Before, a builder agent's mapping with a sibling key (for example "event": "$.event.attributes") showed as an empty box, and a save dropped that key.

Where the code sits, mapped to backend layers:

  • @agenta/entities/gatewayTrigger/core is the pure-function layer, like a core module with pytest tests: the schema-to-cards rules, the template read and write, the preview text, and the newest-event pick. The event text format and the value rule (a string unchanged, null empty, anything else compact JSON) mirror the Python ones and are pinned by the same fixtures.
  • @agenta/entity-ui holds the two reusable components: EventMessageComposer (over a restored PillEditor) and EventFieldCards.
  • @agenta/automation-ui wires them into the Instruction field and adds includeEvent to the unsaved form state of the create and detail screens (the "draft", like a request body built field by field until Save).
  • web/mobile changes the Run now button and menu item.

The Fern client types for TriggerSubscriptionData and TriggerDeliveryData are regenerated from the EE OpenAPI spec of a stack that runs the backend branch. The run also changed two unrelated generated files (a docstring from another endpoint and the default server URL); they are left out.

Scope and risk

  • Event automations on /m only. The classic app under /w is not touched.
  • An old automation opens with the checkbox checked, because the backend reads a missing key as on. Saving it writes include_event: true explicitly.
  • Typed text that starts with $ or / is still read as a selector by the backend. This is a known limit and is not changed here.

Tests

  • @agenta/entities unit tests (vitest): 186 files, 2638 tests pass. New tests cover the seven GitHub pull request cards and labels, a nested Linear-style group, bracket selectors and a quoted key with a dot, sibling keys kept on write, a pill moved from a completion shape to a chat shape, the newest event from unsorted rows, the preview with and without an event, the value fixtures (string, number, boolean, object, array, absent), and the shared event text example.
  • web/mobile unit tests: 120 files, 720 tests pass, including a new test for the Run now text (with a delivery, with none, with a failed call, and with a mapping the composer cannot show).
  • Type checks pass for @agenta/entities, @agenta/entity-ui, @agenta/automation-ui and web/mobile. pnpm lint-fix is clean. Storybook lints and builds, with a new EventMessageComposer story.
  • Live check on a local EE stack running both branches, in /m, as a new account:
    • Detail screen of an automation saved before this change: the checkbox is checked. Unchecking shows the save bar and Discard checks it again. Uncheck, Save, reload: still unchecked.
    • Typing text and clicking "Title" adds a pill and checks the card. The stored mapping has the $.event.attributes.title part. Backspace and the x both remove the pill.
    • After one signed GitHub pull request event, the preview shows the real title in place of the pill and the event block. The text matches what the dispatcher sent, except for the key order inside the event JSON (Postgres stores the event as jsonb, which reorders keys).
    • At 390 px the cards are one column and the page does not scroll sideways.
  • Not checked live: Run now and the create step. The local stack has no real GitHub connection and the test agent did not appear in the agent picker, so neither could start. The session workspace drawer was not opened; it renders the same component.

What to QA

  • Open an event automation (GitHub pull request event) on /m. Under the Instruction box, cards show with Composio's descriptions. Click "Title": a pill appears and the card shows a check.
  • The checkbox reads "Also attach the full event, so the agent can use any detail" and is checked on an automation made before this release. Uncheck, Save, reload: unchecked. Discard before Save brings it back.
  • Make a pull request in the connected repo. Reopen the automation: the preview shows the real title and the event JSON. Run now opens a chat whose first message has the same text.
  • Create a new event automation with a pill and save it. The run that follows gets the title in the message.
  • Regression: a schedule automation still shows the plain Instruction box with "Sent to the agent on every run."

Agenta Product Agent added 3 commits October 29, 2026 19:29
Event automations get a pill composer over the instruction, field cards
from the catalog payload schema, an include-event checkbox and a preview
of the message the agent gets. Run now sends the preview text.

Entire-Checkpoint: 01M64ERHZ1AV2Q0Y69M85VKGA1
… the EE spec

Entire-Checkpoint: 01M64EX794ZT4M492N6GHXCF64
… the preview rules in the spec

Entire-Checkpoint: 01M64GTB160EB5N60Z2PAN9B8M
@coderabbitai

coderabbitai Bot commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

Review in Change Stack →

📝 Summary

Summary by CodeRabbit

  • New Features
    • Event automations now offer selectable field tags inside the instruction editor, with descriptions and clear indicators for fields already used.
    • Choose whether event details appear in the message, and preview the message using the latest delivery when available.
    • Run now uses the automation’s configured message and event data.
  • Bug Fixes
    • Selectors now support keys with special characters or leading digits, and message edits preserve other input values.

This change adds schema-derived event tags and a pill-based message editor for event automations. It preserves unrelated mapping keys, previews selectors against the latest delivery event, stores the event-inclusion setting, and resolves event-aware text for Run now.

Changes: Event automation messages

Layer / File(s) Summary
Event data, templates, and previews
web/packages/agenta-entities/src/gatewayTrigger/core/*, web/packages/agenta-entities/src/gatewayTrigger/index.ts, web/packages/agenta-entities/tests/unit/gatewayTrigger*
Adds helpers for schema-derived fields, selector parsing, message-template compilation and remapping, event previews, and latest-delivery selection. The message-template tests cover preserving other mapping keys and unsupported mappings.
Event message editor
web/packages/agenta-entity-ui/src/gatewayTrigger/drawers/subscription/*, web/packages/agenta-entity-ui/src/gatewayTrigger/index.ts, web/packages/agenta-entity-ui/tests/unit/*, web/storybook/stories/entity-ui/EventMessageComposer.stories.tsx, openspec/changes/attach-event-to-automation-runs/{proposal.md,design.md,specs/automation-event-fields/spec.md,tasks.md}
Adds the pill editor, event message composer, and event-field tags. The editor supports selector insertion and template-aware clipboard actions; the specifications and Storybook story describe and demonstrate the tag-based UI.
Automation drafts and event instruction UI
web/packages/agenta-automation-ui/src/{AutomationCreateBody.tsx,AutomationDetailBody.tsx,AutomationDrawer.tsx,AutomationInstructionField.tsx,automationEdit.ts,useAutomationCreate.ts,useAutomationDraft.ts}, web/mobile/src/features/automations/AutomationDetailScreen.tsx, openspec/changes/attach-event-to-automation-runs/{specs/automation-event-fields/spec.md,tasks.md}
Carries includeEvent through create and edit drafts, previews, and subscription payloads. Event automations use event fields and delivery data in the instruction editor and preview.
Run now text generation
web/mobile/src/features/automations/{AutomationActionsMenu.tsx,AutomationTestRunButton.tsx,runNowText.ts}, web/mobile/tests/unit/automationRunNowText.test.ts, openspec/changes/attach-event-to-automation-runs/{design.md,tasks.md}
Run now resolves text using delivery events for supported event mappings. It does not start a session when text resolution returns no value or delivery lookup fails.

Priority: Normal

Estimated code review effort: 4 (Complex) | ~60 minutes

Sequence Diagram(s)

sequenceDiagram
  participant AutomationActionsMenu
  participant runNowText
  participant queryTriggerDeliveries
  participant latestDeliveryEvent
  participant TaskSession
  AutomationActionsMenu->>runNowText: resolve automation run text
  runNowText->>queryTriggerDeliveries: fetch trigger deliveries
  queryTriggerDeliveries-->>runNowText: return delivery rows
  runNowText->>latestDeliveryEvent: select latest event-bearing delivery
  latestDeliveryEvent-->>runNowText: return event or null
  runNowText-->>AutomationActionsMenu: return text or null
  AutomationActionsMenu->>TaskSession: start session when text is truthy
Loading

Possibly related issues

  • Agenta-AI/agenta issue 7914: The PR adds frontend event-aware preview and Run now resolution, but does not change the backend resolver behavior described in the issue.
Merge Risk: Low · up to 90bf8

Run now blocks empty messages as intended. Add a name for the instruction textbox and correct the event warning. These bounded issues do not prevent merging.

Pre-merge checks: Passed 5
Check name Status Explanation
Title check Passed The title clearly and concisely describes the primary change: adding event-field selection to event automation instructions.
Description check Passed The description is directly related to the changeset and explains event-field pills, previews, event inclusion, Run now behavior, testing, and known limitations.
Docstring Coverage Passed Docstring coverage is 70.00% which is sufficient. The required threshold is 60.00%. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentati…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage

Explanation

Docstring coverage is 70.00% which is sufficient. The required threshold is 60.00%. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 30 functions across 28 files. (4 skipped: 4 unsupported.)

Finishing Touches
📝 Generate docstrings
  • Commit to this branch
  • Create a new PR
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • 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

Comment @coderabbitai help to get the list of available commands.

@mmabrouk

Copy link
Copy Markdown
Member Author

🤖 The AI agent says: @coderabbitai review

@coderabbitai

coderabbitai Bot commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

@mmabrouk I will review the PR changes.

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@github-actions

github-actions Bot commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

Website preview

Preview URL: https://pr-7913-agenta-website-preview.mahmoud-637.workers.dev

Built from b2eda637727fa17432281b7d8d2940229d7ebfbf. This comment updates in place on every push.

@coderabbitai coderabbitai 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.

Actionable comments posted: 3


Review info
Run configuration
Commits

Reviewing files that changed from the base of the PR and between 93e75b2 and 161a3a3.

Files ignored due to path filters: 2
  • web/packages/agenta-api-client/src/generated/api/types/TriggerDeliveryData.ts is excluded by !**/generated/**
  • web/packages/agenta-api-client/src/generated/api/types/TriggerSubscriptionData.ts is excluded by !**/generated/**
Files selected for processing: 30
  • openspec/changes/attach-event-to-automation-runs/design.md
  • openspec/changes/attach-event-to-automation-runs/specs/automation-event-fields/spec.md
  • openspec/changes/attach-event-to-automation-runs/tasks.md
  • web/mobile/src/features/automations/AutomationActionsMenu.tsx
  • web/mobile/src/features/automations/AutomationDetailScreen.tsx
  • web/mobile/src/features/automations/AutomationTestRunButton.tsx
  • web/mobile/src/features/automations/runNowText.ts
  • web/mobile/tests/unit/automationRunNowText.test.ts
  • web/packages/agenta-automation-ui/src/AutomationCreateBody.tsx
  • web/packages/agenta-automation-ui/src/AutomationDetailBody.tsx
  • web/packages/agenta-automation-ui/src/AutomationDrawer.tsx
  • web/packages/agenta-automation-ui/src/AutomationInstructionField.tsx
  • web/packages/agenta-automation-ui/src/automationEdit.ts
  • web/packages/agenta-automation-ui/src/useAutomationCreate.ts
  • web/packages/agenta-automation-ui/src/useAutomationDraft.ts
  • web/packages/agenta-entities/src/gatewayTrigger/core/eventFields.ts
  • web/packages/agenta-entities/src/gatewayTrigger/core/eventMessageTemplate.ts
  • web/packages/agenta-entities/src/gatewayTrigger/core/eventPreview.ts
  • web/packages/agenta-entities/src/gatewayTrigger/core/latestDeliveryEvent.ts
  • web/packages/agenta-entities/src/gatewayTrigger/core/selectorPreview.ts
  • web/packages/agenta-entities/src/gatewayTrigger/core/types.ts
  • web/packages/agenta-entities/src/gatewayTrigger/index.ts
  • web/packages/agenta-entities/tests/unit/gatewayTriggerEventFields.test.ts
  • web/packages/agenta-entities/tests/unit/gatewayTriggerEventMessageTemplate.test.ts
  • web/packages/agenta-entities/tests/unit/gatewayTriggerSelectorPreview.test.ts
  • web/packages/agenta-entity-ui/src/gatewayTrigger/drawers/subscription/EventFieldCards.tsx
  • web/packages/agenta-entity-ui/src/gatewayTrigger/drawers/subscription/EventMessageComposer.tsx
  • web/packages/agenta-entity-ui/src/gatewayTrigger/drawers/subscription/PillEditor.tsx
  • web/packages/agenta-entity-ui/src/gatewayTrigger/index.ts
  • web/storybook/stories/entity-ui/EventMessageComposer.stories.tsx

Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 6 remain after this review.

@github-actions

github-actions Bot commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

Railway Preview Environment

Item Value
Status stopped
Commit 90bf87e9534e5767d994143747c71768f5d0d44c
Manual expiry (UTC) Not granted
CI deadline (UTC) Not granted
Workflow https://github.com/Agenta-AI/agenta/actions/runs/40951783281

PR closed or converted to draft. Environment absence verified; retained storage requires separate provider accounting.

Post /preview as a new comment to request a one-hour preview. Repeating it while active does not extend the hour.
Preview data is disposable. Expiry is enforced by the next successful cleanup sweep, not an exact timer.
Environment deletion stops its compute. Provider-retained storage and permanent services may still be billed.

Agenta Product Agent added 2 commits October 29, 2026 20:27
…n box

The field cards took too much room. Each field is now a small tag that looks like the
pill it adds, in one wrapping row inside the instruction box. The provider's description
moves into a tooltip on hover and keyboard focus. The header row above the cards is gone.
The field list is flat, because the group headers it fed are gone.

Entire-Checkpoint: 01M64J8KYFT5DFYVC0JHZNTXBB
…ditor props

The selector-to-label map always gave the same label as the selector itself, so the
preview, the composer and Run now now call selectorLabel(selector). The placeholder and
disabled props had no caller. Helpers only used inside @agenta/entities are no longer
exported.

Entire-Checkpoint: 01M64JVY0KT8REGGPFMXC27ASN
@mmabrouk

Copy link
Copy Markdown
Member Author

🤖 The AI agent says: QA record for this PR (stacked on #7911).

Heads tested. Backend #7911: 93e75b2d7f. This PR: 6e03bc4e5d (small field tags inside the instruction box). The first test run was on 161a3a3f4b.

Tests

  • API triggers unit tests: 251 passed, 4 skipped (the skips need a Postgres the test cannot reach).
  • SDK unit tests for the op catalog and builder reference: 79 passed.
  • Web entities vitest: 2639 passed. Mobile vitest: 720 passed (one run lost 3 files when workers ran out of memory; a rerun alone passed all).

Live checks as a real user in /m, on a local stack, with an account made for the test

  • Backend, four rows, one signed event each: an old row with no include_event key gets the event in the agent's message. include_event false sends the instruction alone. A pill on the number field sends "42" as text and the run does not fail. An empty mapping {} sends the event as the message. PASS.
  • Detail page: an old automation shows the checkbox checked. A tag click adds a pill, the pill's X removes it. Save and reload keep the pill and the checkbox (unchecked also persists). After an event, the preview shows the real title. PASS.
  • Run now: with a delivery, the session's first message is the preview text. With no delivery, the message is Review PR number [Number] with no event block. PASS.
  • The automation drawer in the agent workspace shows the same field. PASS.
  • Phone width 390 px: one column, no sideways scroll. PASS.
  • Hover on a tag shows its description. PASS.

Blocked, not failed

  • Create flow, last click: the page, agent picker (agent made in /m), event, owner and repo, pill and preview all work. The final "Create automation" cannot finish because the stack has no real GitHub connection, so the provider refuses the stand-in connection (answer 424; I did not capture the body).
  • Spec task 12.1, a real Composio GitHub delivery: needs a GitHub account made for QA and a webhook address Composio can reach. Neither exists here. The schema keys and the payload size are still unchecked against a real delivery.

Minor findings

  • The preview lists event keys in a different order than the agent receives them (same content).
  • An agent created only through /simple/workflows does not appear in the automation Agent picker. An agent made in /m does.

The headline recording (open an event automation, add a Title pill, see the preview, save, fire an event, see the real title) could not be attached here, because gh cannot upload media. It is kept with the QA evidence.

Agenta Product Agent added 5 commits October 29, 2026 20:46
…form

The backend's JSONPath parser rejects a dot step such as $.event.attributes.123, so
that pill reached the agent as empty text while the preview showed the value.

Entire-Checkpoint: 01M64K7G4QDY1MDFDG0Q8HN5VV
… does not add it

The dispatcher adds the event only to a messages list or to empty inputs. For an agent
whose instruction goes under another input key, the preview showed an event block that the
agent never got. addsEventText states the backend rule once for the preview.

Entire-Checkpoint: 01M64KF40JAPC6T01N2ENE1DAX
…eturn null on failure

includesEvent states that a subscription saved without the key reads as on; the draft and
Run now both call it. runNowText now logs a failed deliveries call and returns null, so the
detail button and the list menu no longer each wrap it in the same try/catch. It also uses
addsEventText, the same rule the preview uses.

Entire-Checkpoint: 01M64KRZFD3CMT8B8G8X8GVR3V
Copy put only the visible text on the clipboard, so a pasted pill came back as plain
label text and stopped filling in. Copy and cut now also write the template under an
application/x-agenta-template entry, and paste rebuilds the pills from it. Other apps
still get readable text, with each pill as its label.

Entire-Checkpoint: 01M64M6FWS6FC0RJ9RYQ9AHWW3
…mpty

A pill alone on a field the newest event lacks resolves to empty text. Run now then
opened a new session with nothing to send. Both Run now entry points now start only
when there is text.

Entire-Checkpoint: 01M64MGGKB8YJ6M3GWX7AKZZGC
@mmabrouk mmabrouk added lgtm This PR has been approved by a maintainer merge queue In the release merge queue; an agent is landing it labels Oct 29, 2026
@mmabrouk

Copy link
Copy Markdown
Member Author

🤖 The AI agent says: Status for the release merge queue (v0.127.2).

The building session has stopped pushing to this branch. The queue can merge it at 7f233f32a8.

  • QA ran on 6e03bc4e5d, and 6 of 8 checks pass. The record is in an earlier comment.
  • The 5 commits after that head are small review fixes: pill copy and paste, field keys that start with a digit, the preview when the dispatcher adds no event, and "Run now" with an empty message. The /m screen checks did not run again on them.
  • A few more review fixes were not pushed. They will come as a small follow-up PR against release/v0.127.2 after this PR merges, so that nothing changes under the merge queue.

Two checks are blocked locally. They need a real GitHub account connected through Composio, so they should run during staging QA:

  1. In /m, finish "Create automation" for a GitHub pull request event with a Title pill.
  2. Open one real pull request. Check that the agent's first message has the real title followed by the Event data (GITHUB_PULL_REQUEST_EVENT): block. Also compare the delivered payload keys with the schema keys: action, createdAt, createdBy, description, number, title, url.

If the keys differ, the pills come out empty. The agent still gets the full event, because the event is included by default, so this is not a release blocker.

Deferred and not needed for this release: #7914.

@mmabrouk

Copy link
Copy Markdown
Member Author

🤖 The AI agent says:

Review loop result for head 7f233f32a8 (base 93e75b2d7f), 2 rounds. Lenses: slop, simplify,
correctness, security, and a design-interfaces check of the stored pill shape and the include_event read.

Lens Round 1 Round 2
Slop Medium Low
Simplify Low Low
Correctness Medium Low
Security Low Low
Interfaces Medium Low

Fixed: copy, cut and paste keep pills (b6862f6); a key that starts with a digit uses bracket form (65ee14b); the preview adds the event block only where the dispatcher does (c8644ba); redundant label map, unused props and exports removed (10a604a); one include_event reader and Run now returns null on failure (9dc7b1c); Run now opens no session for empty text (7f233f3).
Left on purpose: text that starts with "$" or "/" is read as a selector by the backend, tracked in #7914; Run now for an empty instruction stays blocked, because the other path needs a message with no approved text; the event composer's warning says "schedule", left for Mahmoud to word.

@mmabrouk
mmabrouk changed the base branch from feat/trigger-include-event to release/v0.127.2 October 29, 2026 20:44

@coderabbitai coderabbitai 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.

Actionable comments posted: 1


Review info
Run configuration
Commits

Reviewing files that changed from the base of the PR and between 161a3a3 and 90bf87e.

Files ignored due to path filters: 2
  • web/packages/agenta-api-client/src/generated/api/types/TriggerDeliveryData.ts is excluded by !**/generated/**
  • web/packages/agenta-api-client/src/generated/api/types/TriggerSubscriptionData.ts is excluded by !**/generated/**
Files selected for processing: 21
  • openspec/changes/attach-event-to-automation-runs/design.md
  • openspec/changes/attach-event-to-automation-runs/proposal.md
  • openspec/changes/attach-event-to-automation-runs/specs/automation-event-fields/spec.md
  • openspec/changes/attach-event-to-automation-runs/tasks.md
  • web/mobile/src/features/automations/AutomationActionsMenu.tsx
  • web/mobile/src/features/automations/AutomationTestRunButton.tsx
  • web/mobile/src/features/automations/runNowText.ts
  • web/mobile/tests/unit/automationRunNowText.test.ts
  • web/packages/agenta-automation-ui/src/AutomationInstructionField.tsx
  • web/packages/agenta-automation-ui/src/useAutomationDraft.ts
  • web/packages/agenta-entities/src/gatewayTrigger/core/eventFields.ts
  • web/packages/agenta-entities/src/gatewayTrigger/core/eventMessageTemplate.ts
  • web/packages/agenta-entities/src/gatewayTrigger/core/eventPreview.ts
  • web/packages/agenta-entities/src/gatewayTrigger/index.ts
  • web/packages/agenta-entities/tests/unit/gatewayTriggerEventFields.test.ts
  • web/packages/agenta-entity-ui/src/gatewayTrigger/drawers/subscription/EventFieldTags.tsx
  • web/packages/agenta-entity-ui/src/gatewayTrigger/drawers/subscription/EventMessageComposer.tsx
  • web/packages/agenta-entity-ui/src/gatewayTrigger/drawers/subscription/PillEditor.tsx
  • web/packages/agenta-entity-ui/src/gatewayTrigger/index.ts
  • web/packages/agenta-entity-ui/tests/unit/pillEditorClipboard.render.test.tsx
  • web/storybook/stories/entity-ui/EventMessageComposer.stories.tsx

Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 5 remain after this review.

@mmabrouk
mmabrouk merged commit 7482a0c into release/v0.127.2 Oct 29, 2026
14 of 15 checks passed
@mmabrouk mmabrouk removed the merge queue In the release merge queue; an agent is landing it label Oct 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lgtm This PR has been approved by a maintainer

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant