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
Analyse the FocusLogger repository and pick one improvement worth shipping next (or a small bundle of trivial wins in the same area). Look at the code, existing features, plans, and TODOs — and at how comparable projects solve similar problems — to find the highest-leverage idea that:
Delivers a real, user-visible benefit
Is the easiest available win at that level of impact
Does not duplicate something the project already does
Is not already in flight elsewhere
When you have picked one:
Create a new issue in this repository describing the actual feature to implement — its user-visible benefit, a one-sentence v0 scope, and any context an implementer will need. This new issue is the real work ticket that the next agent pickup will turn into code.
Then close this issue with a one-line comment referencing the new feature issue you filed.
AI agent: load and follow the work-item-improvement skill.
[AI Review]
· Story Points: 2
· Difficulty: None (0)
· Impact: Very High (4)
· AI Work: 85%
· Human Work: 15%
Review Summary
Skill Matrix: C# / .NET 8, WPF, System.Windows.Forms.NotifyIcon, Windows API / P/Invoke, GitHub issue management
Story Points (reasons): - Work type: Administrative/process meta-ticket — baseline 1–2; deliverables are filing a new FEAT GitHub issue and closing this TECH issue with a reference comment, not implementing any code. - Calibration match: All codebase research is already complete (Qdrant searches confirmed scope, files, and constraints); remaining work is composing and submitting a well-formed issue description, which aligns with the '2 — few hours' anchor. - Codebase context: Pre-analysis confirmed the feature content, affected files, and implementer notes in full — no further investigation needed; the SolverAgent executes predetermined, well-defined steps. - No adjustment — AC specifies only the FEAT issue creation and TECH issue closure; no staged rollout, performance requirements, or cross-team coordination is required.
Split recommendation: No
Notes: The story is a well-scoped meta-ticket: analyse the FocusLogger codebase, pick the single highest-leverage improvement, create a properly-labelled FEAT issue for it, then close this TECH issue with a reference comment.
Qdrant searches confirmed all key facts: - `FocusLogger/MainWindow.xaml.cs`: `IsClosing` static bool is the only shutdown signal; `Window_Closing` sets it to `true` unconditionally and does not cancel the close event. No tray or hide-to-tray logic exists. - `FocusLogger/Controls/DataListControl.xaml.cs`: `_Timer_Elapsed` returns immediately when `MainWindow.IsClosing == true`, so the 1 ms polling timer stops on the first timer fire after close. For hide-to-tray, `IsClosing` must remain `false`. - `FocusLogger/JocysCom.FocusLogger.csproj`: `true` is already present, making `System.Windows.Forms.NotifyIcon` available at zero new-dependency cost. `App.ico` means the icon asset is already embedded. - `FocusLogger/App.xaml.cs`: No tray icon initialisation; clean insertion point exists. - `FocusLogger.Tests/UIAutomationTests.cs`: Tests call `appProcess.Kill()` for teardown — this bypasses `WM_CLOSE`, so intercepting `Window_Closing` will not break the test suite.
Chosen improvement (as confirmed in Summary): **FEAT: Minimize to system tray**. This directly unblocks the canonical background-monitoring workflow described in `FocusLogger/Resources/AiAnalysisPrompt.md` and is the highest-leverage improvement available: zero new dependencies, ~50-line change, large user-visible benefit for the primary gamer/power-user audience.
Coding guidelines (`.ai/coding-guideline.instructions.md`) require: issue title pattern `FEAT: {Description}`, no NuGet packages (satisfied), and this TECH issue must be closed with a one-line comment referencing the new FEAT issue number.
No clarifying questions are needed — all context is fully resolved by the repository analysis and Qdrant searches.
Clarifying Questions from Developer: None
Proposed Solution: **Step 1 — Create the FEAT issue (primary deliverable of this TECH ticket)** File a new GitHub issue titled exactly `FEAT: Minimize to system tray` containing: - User-visible benefit: closing the window hides to tray so logging continues silently; double-click or tray-menu 'Show' restores the window; 'Exit' shuts down completely. - v0 scope: intercept `Window_Closing` → cancel close → `this.Hide()` → show `NotifyIcon`; double-click restores; right-click menu provides Show/Exit. - Implementer notes: `UseWindowsForms` already enabled; use `App.ico` for the tray icon; `IsClosing` must only become `true` on real Exit, not on hide.
**Step 2 — Implement the feature in `FocusLogger/MainWindow.xaml.cs`** 1. Add a `System.Windows.Forms.NotifyIcon _trayIcon` field. 2. In `MainWindow()` constructor (after `InitializeComponent`): initialise `_trayIcon` with `App.ico`, a tooltip of `"FocusLogger"`, and a context menu with two items — 'Show' (calls `RestoreWindow()`) and 'Exit' (calls `ExitApp()`). 3. Wire `_trayIcon.DoubleClick` to `RestoreWindow()`. 4. Replace the body of `Window_Closing` with: `e.Cancel = true; this.Hide(); _trayIcon.Visible = true;` 5. `RestoreWindow()`: `_trayIcon.Visible = false; this.Show(); this.WindowState = WindowState.Normal; this.Activate();` 6. `ExitApp()`: `IsClosing = true; _trayIcon.Dispose(); Application.Current.Shutdown();`
**Step 3 — Close this TECH issue** Add comment: `Closing in favour of #.` then close the issue.
Solver Agent Prompt: Use to instruct other AI agents (e.g., CoPilot, CLINE...) to implement the solution.
**Work Item to Address:**
Title: TECH: FocusLogger Improvement
Description:
Analyse the FocusLogger repository and pick one improvement worth shipping next (or a small bundle of trivial wins in the same area). Look at the code, existing features, plans, and TODOs — and at how comparable projects solve similar problems — to find the highest-leverage idea that:
Delivers a real, user-visible benefit
Is the easiest available win at that level of impact
Does not duplicate something the project already does
Is not already in flight elsewhere
When you have picked one:
Create a new issue in this repository describing the actual feature to implement — its user-visible benefit, a one-sentence v0 scope, and any context an implementer will need. The new issue title must follow the FEAT: {Description} naming convention.
Then close this issue with a one-line comment referencing the new feature issue you filed.
> AI agent: load and follow the work-item-improvement skill.
Acceptance Criteria: (none specified — deliverables are the new FEAT issue and the closure of this TECH issue)
Pre-analysis summary (already completed):
The chosen improvement is FEAT: Minimize to system tray.
Rationale:
FocusLogger's primary audience is gamers and power users who need silent background monitoring. Currently, clicking X terminates the process and all in-memory log data is lost.
UseWindowsForms is already enabled in the .csproj (<UseWindowsForms>true</UseWindowsForms>), so System.Windows.Forms.NotifyIcon is available with zero new NuGet dependencies.
App.ico is already present and set as the application icon — it can be reused directly as the tray icon.
The change is confined to MainWindow.xaml.cs (~50 lines): intercept Window_Closing to hide instead of close, show a tray icon, provide Show/Exit context menu, and ensure MainWindow.IsClosing is only set true on real Exit so the 1 ms polling timer in DataListControl keeps running while hidden.
No open issues or branches reference this feature. It is not duplicated anywhere in the codebase.
Coding guidelines require the new issue title to follow: FEAT: Minimize to system tray.
This TECH issue must be closed with a one-line comment referencing the new FEAT issue number.
Potentially Relevant Files/Artifacts:
.ai/repository-analysis.instructions.md
.ai/coding-guideline.instructions.md
FocusLogger/MainWindow.xaml.cs
FocusLogger/MainWindow.xaml
FocusLogger/App.xaml.cs
FocusLogger/App.xaml
FocusLogger/JocysCom.FocusLogger.csproj
FocusLogger/Controls/DataListControl.xaml.cs
FocusLogger/Common/DataItem.cs
FocusLogger/Resources/AiAnalysisPrompt.md
FocusLogger.Tests/UIAutomationTests.cs
Please analyse this work item and the provided context. Your tasks are:
Create a new GitHub issue titled FEAT: Minimize to system tray with a clear description of the user-visible benefit, v0 scope, and implementer notes.
Close this TECH issue with a one-line comment referencing the new FEAT issue number.
Your working directory will be the root of the repository.
Activity
EvoJocys commentedon May 23, 2026
[AI Review]
· Story Points: 2
· Difficulty: None (0)
· Impact: Very High (4)
· AI Work: 85%
· Human Work: 15%
Review Summary
Skill Matrix: C# / .NET 8, WPF, System.Windows.Forms.NotifyIcon, Windows API / P/Invoke, GitHub issue management
Story Points (reasons):
- Work type: Administrative/process meta-ticket — baseline 1–2; deliverables are filing a new FEAT GitHub issue and closing this TECH issue with a reference comment, not implementing any code.
- Calibration match: All codebase research is already complete (Qdrant searches confirmed scope, files, and constraints); remaining work is composing and submitting a well-formed issue description, which aligns with the '2 — few hours' anchor.
- Codebase context: Pre-analysis confirmed the feature content, affected files, and implementer notes in full — no further investigation needed; the SolverAgent executes predetermined, well-defined steps.
- No adjustment — AC specifies only the FEAT issue creation and TECH issue closure; no staged rollout, performance requirements, or cross-team coordination is required.
Split recommendation: No
Notes: The story is a well-scoped meta-ticket: analyse the FocusLogger codebase, pick the single highest-leverage improvement, create a properly-labelled FEAT issue for it, then close this TECH issue with a reference comment.
Qdrant searches confirmed all key facts:
- `FocusLogger/MainWindow.xaml.cs`: `IsClosing` static bool is the only shutdown signal; `Window_Closing` sets it to `true` unconditionally and does not cancel the close event. No tray or hide-to-tray logic exists.
- `FocusLogger/Controls/DataListControl.xaml.cs`: `_Timer_Elapsed` returns immediately when `MainWindow.IsClosing == true`, so the 1 ms polling timer stops on the first timer fire after close. For hide-to-tray, `IsClosing` must remain `false`.
- `FocusLogger/JocysCom.FocusLogger.csproj`: `true` is already present, making `System.Windows.Forms.NotifyIcon` available at zero new-dependency cost. `App.ico` means the icon asset is already embedded.
- `FocusLogger/App.xaml.cs`: No tray icon initialisation; clean insertion point exists.
- `FocusLogger.Tests/UIAutomationTests.cs`: Tests call `appProcess.Kill()` for teardown — this bypasses `WM_CLOSE`, so intercepting `Window_Closing` will not break the test suite.
Chosen improvement (as confirmed in Summary): **FEAT: Minimize to system tray**. This directly unblocks the canonical background-monitoring workflow described in `FocusLogger/Resources/AiAnalysisPrompt.md` and is the highest-leverage improvement available: zero new dependencies, ~50-line change, large user-visible benefit for the primary gamer/power-user audience.
Coding guidelines (`.ai/coding-guideline.instructions.md`) require: issue title pattern `FEAT: {Description}`, no NuGet packages (satisfied), and this TECH issue must be closed with a one-line comment referencing the new FEAT issue number.
No clarifying questions are needed — all context is fully resolved by the repository analysis and Qdrant searches.
Clarifying Questions from Developer:
None
Proposed Solution: **Step 1 — Create the FEAT issue (primary deliverable of this TECH ticket)**
File a new GitHub issue titled exactly `FEAT: Minimize to system tray` containing:
- User-visible benefit: closing the window hides to tray so logging continues silently; double-click or tray-menu 'Show' restores the window; 'Exit' shuts down completely.
- v0 scope: intercept `Window_Closing` → cancel close → `this.Hide()` → show `NotifyIcon`; double-click restores; right-click menu provides Show/Exit.
- Implementer notes: `UseWindowsForms` already enabled; use `App.ico` for the tray icon; `IsClosing` must only become `true` on real Exit, not on hide.
**Step 2 — Implement the feature in `FocusLogger/MainWindow.xaml.cs`**
1. Add a `System.Windows.Forms.NotifyIcon _trayIcon` field.
2. In `MainWindow()` constructor (after `InitializeComponent`): initialise `_trayIcon` with `App.ico`, a tooltip of `"FocusLogger"`, and a context menu with two items — 'Show' (calls `RestoreWindow()`) and 'Exit' (calls `ExitApp()`).
3. Wire `_trayIcon.DoubleClick` to `RestoreWindow()`.
4. Replace the body of `Window_Closing` with: `e.Cancel = true; this.Hide(); _trayIcon.Visible = true;`
5. `RestoreWindow()`: `_trayIcon.Visible = false; this.Show(); this.WindowState = WindowState.Normal; this.Activate();`
6. `ExitApp()`: `IsClosing = true; _trayIcon.Dispose(); Application.Current.Shutdown();`
**Step 3 — Close this TECH issue**
Add comment: `Closing in favour of #.` then close the issue.
Related Items:
.ai/repository-analysis.instructions.md
FocusLogger/MainWindow.xaml.cs
FocusLogger/App.xaml.cs
FocusLogger/Controls/DataListControl.xaml.cs (UpdateInfo / InitTimer)
.ai/coding-guideline.instructions.md
FocusLogger/Common/DataItem.cs
FocusLogger/Resources/AiAnalysisPrompt.md
FocusLogger.Tests/UIAutomationTests.cs
Solver Agent Prompt: Use to instruct other AI agents (e.g., CoPilot, CLINE...) to implement the solution.
When you have picked one:
FEAT: {Description}naming convention.> AI agent: load and follow the
work-item-improvementskill.Acceptance Criteria:
(none specified — deliverables are the new FEAT issue and the closure of this TECH issue)
Pre-analysis summary (already completed):
The chosen improvement is
FEAT: Minimize to system tray.Rationale:
UseWindowsFormsis already enabled in the.csproj(<UseWindowsForms>true</UseWindowsForms>), soSystem.Windows.Forms.NotifyIconis available with zero new NuGet dependencies.App.icois already present and set as the application icon — it can be reused directly as the tray icon.MainWindow.xaml.cs(~50 lines): interceptWindow_Closingto hide instead of close, show a tray icon, provide Show/Exit context menu, and ensureMainWindow.IsClosingis only settrueon real Exit so the 1 ms polling timer inDataListControlkeeps running while hidden.FEAT: Minimize to system tray.Potentially Relevant Files/Artifacts:
.ai/repository-analysis.instructions.md.ai/coding-guideline.instructions.mdFocusLogger/MainWindow.xaml.csFocusLogger/MainWindow.xamlFocusLogger/App.xaml.csFocusLogger/App.xamlFocusLogger/JocysCom.FocusLogger.csprojFocusLogger/Controls/DataListControl.xaml.csFocusLogger/Common/DataItem.csFocusLogger/Resources/AiAnalysisPrompt.mdFocusLogger.Tests/UIAutomationTests.csPlease analyse this work item and the provided context. Your tasks are:
FEAT: Minimize to system traywith a clear description of the user-visible benefit, v0 scope, and implementer notes.Your working directory will be the root of the repository.