Skip to content

refactor: v2 - ai assistant - basic chat in RunView#2354

Merged
maxy-shpfy merged 1 commit into
masterfrom
06-02-refactor_v2_-_ai_assistant_-_basic_chat_in_runview
Jun 11, 2026
Merged

refactor: v2 - ai assistant - basic chat in RunView#2354
maxy-shpfy merged 1 commit into
masterfrom
06-02-refactor_v2_-_ai_assistant_-_basic_chat_in_runview

Conversation

@maxy-shpfy

@maxy-shpfy maxy-shpfy commented Jun 3, 2026

Copy link
Copy Markdown
Collaborator

Description

Integrates the AI Assistant chat window into the RunView. The chat window is gated behind the ai-assistant feature flag and is opened automatically when the flag is enabled. The window is persisted, non-closeable by the user, and positioned in the top-left area of the view.

A dedicated read-only tool bridge (runViewToolBridge) is introduced for the RunView AI assistant. Since RunView inspects a completed pipeline run rather than an editable spec, the bridge exposes getPipelineState and validatePipeline as functional operations while all spec-mutating methods (addTask, connectNodes, setTaskArgument, etc.) return { success: false } with an appropriate read-only error message. Run-lifecycle and debug handlers are composed in from the shared bridge utilities.

The AiChatStoreProvider is also added to the RunView provider tree to supply the necessary store context for the chat component.

Related Issue and Pull requests

Type of Change

  • Bug fix
  • New feature
  • Improvement
  • Cleanup/Refactor
  • Breaking change
  • Documentation update

Checklist

  • I have tested this does not break current pipelines / runs functionality
  • I have tested the changes on staging

Screenshots (if applicable)

Demo of AI in RunView - 1.mov (uploaded via Graphite)

Test Instructions

  1. Enable the ai-assistant feature flag.
  2. Open a completed pipeline run in RunView.
  3. Verify the AI Assistant chat window appears automatically and is positioned correctly.
  4. Confirm that read-only operations (viewing pipeline state, validating) work as expected in the chat.
  5. Confirm that any spec-mutating requests from the assistant return an appropriate read-only error.
  6. Disable the ai-assistant flag and verify the chat window closes.

Additional Comments

The read-only constraint is intentional — RunView is not an editing surface, so spec mutations are explicitly blocked at the bridge level rather than relying on UI restrictions alone.

@github-actions

github-actions Bot commented Jun 3, 2026

Copy link
Copy Markdown

🎩 Preview

A preview build has been created at: 06-02-refactor_v2_-_ai_assistant_-_basic_chat_in_runview/89ff444

maxy-shpfy commented Jun 10, 2026

Copy link
Copy Markdown
Collaborator Author

Merge activity

@maxy-shpfy maxy-shpfy changed the base branch from 06-02-refactor_v2_-_ai_assistant_-_move_ai_chat_components_to_shared_space to graphite-base/2354 June 11, 2026 00:04
@maxy-shpfy maxy-shpfy force-pushed the graphite-base/2354 branch from 3556d18 to 8661e4b Compare June 11, 2026 06:01
@maxy-shpfy maxy-shpfy force-pushed the 06-02-refactor_v2_-_ai_assistant_-_basic_chat_in_runview branch from d70a0e6 to 4dcf8e7 Compare June 11, 2026 06:01
@maxy-shpfy maxy-shpfy changed the base branch from graphite-base/2354 to 06-02-refactor_v2_-_ai_assistant_-_move_ai_chat_components_to_shared_space June 11, 2026 06:01
@maxy-shpfy maxy-shpfy changed the base branch from 06-02-refactor_v2_-_ai_assistant_-_move_ai_chat_components_to_shared_space to graphite-base/2354 June 11, 2026 06:05
@maxy-shpfy maxy-shpfy changed the base branch from graphite-base/2354 to master June 11, 2026 06:05
@maxy-shpfy maxy-shpfy force-pushed the 06-02-refactor_v2_-_ai_assistant_-_basic_chat_in_runview branch from 4dcf8e7 to 89ff444 Compare June 11, 2026 06:06
@maxy-shpfy maxy-shpfy merged commit 88e5824 into master Jun 11, 2026
17 checks passed
@maxy-shpfy maxy-shpfy deleted the 06-02-refactor_v2_-_ai_assistant_-_basic_chat_in_runview branch June 11, 2026 06:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants