improvement(copilot): structured metadata context + start block deprecation

[icecrasher321]

Summary

Combining #1345 and #1326

Type of Change

• New feature

Testing

Manually

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
sim	Error			Sep 23, 2025 6:23am

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
docs	Skipped			Sep 23, 2025 6:23am

[greptile-apps]

Greptile Summary

This PR implements a major architectural refactoring that combines two significant improvements: structured metadata context for copilot functionality and deprecation of the unified start block system. The changes introduce a new trigger architecture that separates workflow initiation concerns into dedicated, specialized blocks.

Start Block Deprecation & Trigger System Overhaul
The unified 'starter' block that previously handled multiple trigger types (manual, chat, API, webhook, schedule) through configuration modes has been deprecated in favor of dedicated trigger blocks: ChatTriggerBlock, ApiTriggerBlock, InputTriggerBlock, and WorkflowInputBlock. The starter block is now hidden from the toolbar (hideFromToolbar: true) but remains functional for backward compatibility. This architectural shift provides cleaner separation of concerns, with each trigger type having its own specialized configuration UI and behavior patterns.

Structured Authentication Metadata
All blocks now include explicit authMode declarations using a new AuthMode enum (OAuth, ApiKey, BotToken), replacing implicit authentication requirements mentioned in text descriptions. This standardization enables programmatic understanding of authentication needs across 50+ blocks, supporting better tooling integration and cleaner copilot context generation.

Enhanced Copilot Context System
The copilot metadata system has been restructured with separate endpoints for basic block listing (get-blocks-and-tools) and detailed metadata (get-blocks-metadata). The new system provides hierarchical metadata organization, separating common parameters from operation-specific ones, and filters out UI-specific elements to reduce LLM context overhead.

Workflow Creation & Execution Changes
New workflows now start with empty canvases instead of pre-configured starter blocks, allowing users to explicitly select appropriate triggers. The execution system has been enhanced with TriggerUtils for dynamic trigger detection, proper validation of trigger connectivity, and context-aware start block resolution that handles both new trigger blocks and legacy starter compatibility.

UI/UX Improvements
The toolbar now features a tabbed interface separating 'Blocks' and 'Triggers', with comprehensive trigger selection modals, warning dialogs for invalid configurations, and placeholder components for trigger-less workflows. New components like InputMapping enable sophisticated workflow composition with parent-to-child input mapping capabilities.

Confidence score: 3/5

• This PR introduces complex architectural changes that significantly modify core workflow execution logic, trigger handling, and metadata systems across the entire codebase
• Score reflects the extensive scope of changes affecting critical execution paths, authentication systems, and user workflow creation patterns that could impact existing functionality
• Pay close attention to executor logic in executor/index.ts, trigger validation in TriggerUtils, and the new copilot metadata endpoints which handle complex parameter resolution and filtering logic

_{100 files reviewed, 21 comments}

_{Edit Code Review Bot Settings | Greptile}