feat(workflow): attention nudge when a launch workflow parks on a gate
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript, python
Research direction
Start with the workflow runner and external event buffer in src/profiles/server/routes/workflow.py and src/profiles/server/routes/instance.py, then trace how the App polls /api/notifications and displays port handoff toasts. Add a gate event when a session newly enters a waiting state, and handle it in the web layer with deduplication and focus checks. Done means the gate draws attention through the requested cues without repeating for the same session and step; the issue names no test files.
Written by the indexing model from the issue text.
Description
Problem
When a launch triggers workflow hooks containing ask:/notify: gates, the session parks in waiting_ask/waiting_notify until the user answers. Users who trigger launches via barcode scans or keyboard shortcuts are frequently focused in another application when the gate appears — ProFiles sits in the background with the runner modal open and nothing draws them back. Interactive sessions are kept indefinitely (the TTL purge only drops terminal sessions), so a missed gate can block the rest of a workflow for as long as the app runs.
Evidence
- The only way forward is the
respondroute;src/profiles/server/routes/workflow.py:397-643. The purge atsrc/profiles/server/routes/workflow.py:90-96explicitly keeps interactive sessions (Drop terminal sessions past the TTL (interactive ones are kept)). - A general UI event poll channel already exists and is already polled by the app for port-handoff toasts:
GET /api/notificationsatsrc/profiles/server/routes/instance.py:74(state.external_events_after(after)). - No event is recorded when a session enters a waiting state, and no OS-level attention mechanism (toast,
document.titleflash, notification) exists anywhere in the web layer today.
Proposed approach
- Server: when the session runner parks on
waiting_ask/waiting_notify/ notice, push an event into the existing external-events buffer (same channel the port handoff uses), carrying session id + gate kind. - Web: the App-level notifications poll already runs — on a gate event, show a toast, flash
document.title, and fire a Web Notification where the environment permits. Fire only when the gate is newly reached (dedupe per session+step), and skip when the document has focus. - Desktop (optional stretch): a pywebview-specific attention request kept inside
profiles.desktop, per the AGENTS.md layering rules (presentation layer only). - Scope S-M. No breaking change — additive event + UI behaviour.
Alternatives considered
- Auto-timeout on gates — changes workflow semantics and could auto-launch or auto-skip against the user's intent; rejected.
- Sound-only cue — poor accessibility and lost on muted systems; toast + title flash is quieter, testable headlessly (vitest), and composes with the existing toast component.
Proposed during automated enhancement scan 2026-11-04
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 4h 46m
- Merged PRs (30d)
- 55
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from falbany/ProFiles
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
falbany/ProFiles#187 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug frontend
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug frontend
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug frontend
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
All issues in falbany/ProFiles
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ip-tools/patzilla#219 · 2 comments ·
Maintainers usually reply within 1 day
-
EPSSClient commits to its SQLite cache once per score: a 100-CVE bulk fetch makes 101 disk flushesOpenpriority:p3 technical-debt
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jimmy058910/jmo-security-repo#1673 ·
Maintainers usually reply within 1 day
-
enhancement ready
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
integration: frontier_silicon
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
home-assistant/core#193176 · 2 comments ·
Maintainers usually reply within 1 day
-
task create and task update take --body-file and --stdinPossibly taken @JuanBarriosS claimed this today. Opencli enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
pyrite-wiki/pyrite#1687 · 1 comment ·
Maintainers usually reply within 1 day