Skip to content

feat: compare two models side by side in split view - #2070

Draft
Douglasymlai wants to merge 1 commit into
mainfrom
feat/split-view-model-comparison
Draft

Douglasymlai wants to merge 1 commit into
mainfrom
feat/split-view-model-comparison

Conversation

@Douglasymlai

Copy link
Copy Markdown
Contributor

Pull Request

Related Issue

N/A — maintainer-directed work; no linked issue required for this PR.

Description

Draft. This branch only adds the shared plan, docs/session-split-view-plan.md, so far. The implementation for this part (§6 of the plan) will follow on this branch.

Problem

Today a Space shows one Session at a time with a fixed summary rail on the right. People want a simpler Session view, two or three things side by side in one Space, model comparison as two Sessions next to each other, and a way to open a Session on its own.

Approach

The plan splits the work into six pull requests: a simpler Session layout, Sessions that can render side by side, split view, model comparison in split view, a new Session layout, and opening a Session in its own window or tab. Each pull request carries the same plan document.

This PR

Behind a developer option, the new Session composer can run one prompt on two models. Eigent creates two linked Sessions, opens them side by side, and shows a comparison chip next to the Space title with each lane's status. The chip opens a summary with usage numbers and actions to compare answers, compare files, apply one lane, follow up both, or export. Both lanes must start from the same files and not see each other's writes; until that is in place, file-writing comparisons stay disabled.

Builds on

The split view and new Session layout PRs from this plan.

Testing

Not started. This branch only adds the plan document. Testing will follow the acceptance list for this part in the plan (§9).

Testing Evidence (REQUIRED)

  • I have included human-verified testing evidence in this PR.
  • This PR includes frontend/UI changes, and I attached screenshot(s) or screen recording(s).
  • No frontend/UI changes in this PR.

Not yet available: the branch currently contains only the plan document.

What is the purpose of this pull request?

  • Bug fix
  • New Feature
  • Documentation update
  • Other

Contribution Guidelines Acknowledgement

This branch has not been deployed

No deployments
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.

1 participant