better progress message on cards#224
Conversation
There was a problem hiding this comment.
Pull request overview
Updates user-facing progress text during LLM batch reprocessing and refines the “Detailed Summary” prompt formatting guidelines used by the AI providers.
Changes:
- Prefixes the retry UI step labels with
1/2and2/2for clearer progress indication. - Updates Gemini and ChatCLI detailed-summary prompt specs/examples to include a colon after the time range.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
Dayflow/Dayflow/Views/UI/RetryCoordinator.swift |
Improves displayed progress messages by numbering the two processing steps. |
Dayflow/Dayflow/Core/AI/GeminiPromptPreferences.swift |
Adjusts the detailed summary line format and examples to include a colon delimiter after the time range. |
Dayflow/Dayflow/Core/AI/ChatCLIPromptPreferences.swift |
Mirrors the detailed summary formatting change for ChatCLI prompts (but introduces a small typo in an example). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| Bad example: | ||
| "7:00 AM - 7:30 AM writing Notion doc | ||
| 7:30 AM - 7:35 AM Slack | ||
| 7:30 AM - 7:35: AM Slack |
There was a problem hiding this comment.
There’s a typo in this “Bad example” line: 7:30 AM - 7:35: AM Slack has an extra colon after 7:35, which breaks the time format you specify above. Adjust it to match the intended timestamp format (and, if desired, keep the trailing colon after the time range consistent with the “Format” line).
| 7:30 AM - 7:35: AM Slack | |
| 7:30 AM - 7:35 AM Slack |
| Format each line as: | ||
| [H:MM AM/PM] - [H:MM AM/PM] [specific action] [in app/tool] [on what] | ||
| [H:MM AM/PM] - [H:MM AM/PM]: [specific action] [in app/tool] [on what] | ||
|
|
There was a problem hiding this comment.
The PR title mentions only progress messaging on cards, but this change also updates the LLM prompt spec for detailed summaries (new required colon after the time range, plus updated examples). Consider updating the PR title/description to reflect this behavioral change in prompt output so it’s easier to review/revert independently if needed.
Stack created with Sapling. Best reviewed with ReviewStack.