[General] Using Opus 4.
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
**Mood:** 😊
**Category:** General
Using Opus 4.8 in interactive mode, not sure if relevant. The UI is very shy with comitting unless you very explicitly say that you want commit and PR. But if I say: I want to fix this . It does all the work. But then it always asks "should I commit", yes, "and now should I make PR?" yes. In Copilot Cli you don't asked so much it makes worktree commits and PRs, it infers better that we are in context of a repo, and that the purpose of "fix" is change code, commit and most likely PR.
---
| Field | Value |
| --- | --- |
| App version | 1.0.10 |
| OS | macOS 15.7.4 |
| Theme | Noctis Azureus |
| Path | /chat |
| Tenure | Day 4 (Week 1) |
Contributor guide
Research direction
Start with the /chat experience described in the issue and compare its interactive workflow with the reported Copilot CLI behavior. Define when a request to fix a problem should proceed through repository changes, commits, and pull requests with fewer confirmations; done means the intended workflow is implemented and covered by appropriate interaction tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100