Skip to content

feat(web): settle and restore threads with a keyboard shortcut - #8089

Merged
t3dotgg merged 3 commits into
mainfrom
t3code/settle-thread-shortcut
Aug 25, 2026
Merged

t3dotgg merged 3 commits into
mainfrom
t3code/settle-thread-shortcut

fix(web): settle shortcuts now match the active thread state

e4f0c37
Select commit
Loading
Failed to load commit list.
MacroscopeApp / Macroscope - Effect Service Conventions succeeded Aug 25, 2026 in 1m 1s

All clear

All clear

Details

Note

Your check run agent prompt is: .macroscope/check-run-agents/effect-service-conventions.md
More information about how Check Run Agents work can be found in our Help Center.


🔍 Agent activity — 2 tool calls

💭 This diff is really about keybindings, not Effect services—the changed files just add a command literal and default binding, with the ChatView.tsx change using a React hook and Atom-style result handling unrelated to Effect service creation. I'll do a quick sanity check that useThreadActions exists and glance at the ChatView diff context to confirm nothing else needs attention.

1. browse_code — In apps/web/src/hooks/useThreadActions.ts (or .tsx), what does the hook return — does it expose a settleThread function, and what is its return type (does it return a promise of an Atom command Exit/Result with a _tag)? Also confirm helpers isAtomCommandInterrupted and squashAtomCommandFailure exist and their signatures.

2. git_tools — supportsSettlement|handleUnsettleActiveThread|activeThreadSettled

💭 This PR doesn't create, move, or refactor Effect services in a way that violates conventions, so there are no findings. Since the response must fit the JSON schema despite the instruction to say "All clear" verbatim, I'll set the status to success with title and summary both reading "All clear."


Agent Credits: 49 credits