You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maka's complete, redacted Desktop diagnostic report is available from error surfaces, but silent failures have no reliable collection path. The existing Copy environment info actions omit the bounded main-process logs and Runtime Host evidence that support usually needs.
The renderer-dependent actions are also unreachable when startup fails before the main window opens, even though Electron may already be showing a native error or recovery dialog.
Multi-Host operation also makes “the current Host” insufficient as a diagnostic authority. If the selected/default Host changes between an operation failing and its report being copied, the report can collect an unrelated Host. Renderer-local failures should not be attributed to any Runtime Host at all.
Desired outcome
Provide one context-aware diagnostic pipeline for both manual and error-triggered capture:
Upgrade the About and command-palette actions to Copy diagnostics.
Make the action globally available through Cmd/Ctrl+Shift+D, with a quiet shortcut hint beside the About action and matching entries in the command palette and keyboard-shortcut help.
Add a bilingual Copy diagnostics action to fatal startup failures and startup-blocking native dialogs; copying must preserve the dialog's original repair, retry, wait, or exit decision.
Bind manual capture to the visible task or selected Runtime Host when that authority is known, and otherwise capture the current default Host.
Capture the profile, Session, or Turn that owns a Host-scoped failure when the error is created, rather than inferring it later from UI state.
Produce Desktop-only evidence when no Host authority exists or the intended Host is unavailable; never fall back to an unrelated Host.
Include the environment, bounded and redacted main-process logs, Runtime Host state and logs when available, and bounded Turn evidence for execution failures.
Retain longer redacted log tails within explicit byte budgets that remain practical for clipboard reports, without weakening per-entry bounds or the Runtime Host wire contract.
Keep capture available while About metadata is loading or unavailable, surface copy success or failure, and ensure Host evidence reads cannot leave copying pending indefinitely.
Keep startup-dialog reports Desktop-only because no renderer-established Host authority exists yet; do not guess a Host from mutable default state.
This is a scope clarification from the original manual-entry proposal: manual and error-triggered reports share the same authority boundary, so multi-Host correctness is part of the feature rather than a separate reporting system.
Non-goals
No new log store, automatic upload, telemetry, or crash-reporting backend.
No raw or unbounded log export.
No fallback from a missing targeted Host to the default Host.
AI use
Codex assisted with drafting this scope clarification.
简体中文
问题
Maka 完整且经过脱敏的 Desktop 诊断报告可以从错误界面复制,但静默故障没有可靠的主动采集入口。现有的复制环境信息不包含支持排障通常需要的有界主进程日志和 Runtime Host 证据。
如果主窗口打开前启动失败,依赖 renderer 的入口同样不可达,即使 Electron 此时已经显示原生错误或恢复弹窗,用户仍无法复制诊断信息。
English
Problem
Maka's complete, redacted Desktop diagnostic report is available from error surfaces, but silent failures have no reliable collection path. The existing Copy environment info actions omit the bounded main-process logs and Runtime Host evidence that support usually needs.
The renderer-dependent actions are also unreachable when startup fails before the main window opens, even though Electron may already be showing a native error or recovery dialog.
Multi-Host operation also makes “the current Host” insufficient as a diagnostic authority. If the selected/default Host changes between an operation failing and its report being copied, the report can collect an unrelated Host. Renderer-local failures should not be attributed to any Runtime Host at all.
Desired outcome
Provide one context-aware diagnostic pipeline for both manual and error-triggered capture:
Cmd/Ctrl+Shift+D, with a quiet shortcut hint beside the About action and matching entries in the command palette and keyboard-shortcut help.This is a scope clarification from the original manual-entry proposal: manual and error-triggered reports share the same authority boundary, so multi-Host correctness is part of the feature rather than a separate reporting system.
Non-goals
AI use
Codex assisted with drafting this scope clarification.
简体中文
问题
Maka 完整且经过脱敏的 Desktop 诊断报告可以从错误界面复制,但静默故障没有可靠的主动采集入口。现有的复制环境信息不包含支持排障通常需要的有界主进程日志和 Runtime Host 证据。
如果主窗口打开前启动失败,依赖 renderer 的入口同样不可达,即使 Electron 此时已经显示原生错误或恢复弹窗,用户仍无法复制诊断信息。
在多 Host 场景中,“当前 Host”也不足以作为诊断权威。如果操作失败后、复制报告前选中或默认 Host 发生变化,报告可能采集到无关 Host;纯 Renderer 本地故障则不应归因到任何 Runtime Host。
期望结果
为主动采集和错误触发建立一条统一、上下文感知的诊断链路:
Cmd/Ctrl+Shift+D在全局提供该操作,并在“关于”页操作旁弱提示该快捷键,同时同步显示在命令面板与快捷键帮助中。这是对最初“增加主动入口”方案的范围澄清:主动报告和错误报告共享同一条 authority 边界,因此多 Host 正确性属于本功能本身,而不是另一套报告系统。
非目标
AI 使用
Codex 协助起草了本次范围澄清。