Namespace workflow variables and inline tool call details

[larryro]

Summary

• Namespace workflow template variables: Workflow configs now use explicit namespaces (input., variables., loop.) instead of flat variable references, preventing naming collisions and improving clarity (e.g., {{files}} → {{input.files}}, {{filesToCompare}} → {{variables.filesToCompare}}).
• Initialize variables with namespace prefix: initialize_execution_variables.ts now stores step-defined variables under the variables. namespace.
• Inline tool call details in message info dialog: The message info dialog now shows tool call parameters and results directly in collapsible sections, replacing the previous raw JSON dump with a structured, readable layout.

Test plan

• Verify contract-comparison and contract-generation example workflows execute correctly with namespaced variable references
• Confirm workflow variable initialization properly namespaces under variables.
• Open message info dialog on a message with tool calls and verify parameters/results display correctly
• Verify collapsible tool call sections expand/collapse as expected

🤖 Generated with Claude Code

Summary by CodeRabbit

• Refactor
  • Refactored workflow configurations to use improved data scoping with centralized input and variable management across workflow steps.
  • Streamlined component architecture for tool call display in chat with enhanced state management and better information organization.
  • Optimized variable initialization for improved workflow execution reliability.

[greptile-apps]

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

📝 Walkthrough

Walkthrough

This pull request systematically refactors data access patterns across workflow configurations and TypeScript components. The changes establish a consistent namespacing convention where input parameters are accessed via input.* and accumulated state is stored under variables.*, replacing direct variable references throughout the workflow steps. Additionally, output mapping configurations are renamed from outputMapping to mapping. In the TypeScript layer, the message info dialog component is refactored to extract tool usage rendering into a new reusable ToolCallCard component, and the execution variable initialization logic is updated to nest input data under a dedicated input property rather than spreading it at the top level.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

• Refactor workflow syntax tool and improve variable validation #796: Introduces namespacing for config and variables, nesting variables under variables.*, and switching outputMapping to mapping — directly aligns with the variable structure and naming convention changes implemented in this PR.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the two main changes: namespacing workflow variables and inlining tool call details in the message info dialog.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/namespace-workflow-variables-and-inline-tool-details

📝 Coding Plan

• Generate coding plan for human review comments

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Tip

You can customize the tone of the review comments and chat replies.

Configure the tone_instructions setting to customize the tone of the review comments and chat replies. For example, you can set the tone to Act like a strict teacher, Act like a pirate and more.