@sylphx/flow 3.27.0 → 3.28.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,11 @@
1
1
  # @sylphx/flow
2
2
 
3
+ ## 3.28.0 (2026-04-07)
4
+
5
+ ### ✨ Features
6
+
7
+ - **agent:** ban long sleeps — continuous monitoring over blocking waits (#148) ([b633724](https://github.com/SylphxAI/flow/commit/b633724fa032c3d388b22920fd5ba81176775de8))
8
+
3
9
  ## 3.27.0 (2026-04-04)
4
10
 
5
11
  ### ✨ Features
@@ -109,6 +109,14 @@ Would you stake your reputation on this? Would you ship this to a paying enterpr
109
109
 
110
110
  **Never stop mid-task.** Do not report context usage, session length, or percentage remaining — ever. These metrics are meaningless on large-context models and create false urgency. You have more than enough context. Auto-compaction handles memory management automatically. Your only job is to finish the task. If context were actually exhausted, the system would compact and you'd continue seamlessly — you will never need to warn about it or plan around it.
111
111
 
112
+ **Avoid unnecessary `sleep` commands:**
113
+ - Do not sleep between commands that can run immediately — just run them.
114
+ - If your command is long running and you would like to be notified when it finishes — use `run_in_background`. No sleep needed.
115
+ - Do not retry failing commands in a sleep loop — diagnose the root cause.
116
+ - If waiting for a background task you started with `run_in_background`, you will be notified when it completes — do not poll.
117
+ - If you must poll an external process, use a check command (e.g. `gh run view`) rather than sleeping first.
118
+ - If you must sleep, keep the duration short (1-5 seconds) to avoid blocking the user.
119
+
112
120
  **Document decisions.** Every significant choice needs rationale:
113
121
  - Why this approach over alternatives?
114
122
  - What trade-offs were considered?
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sylphx/flow",
3
- "version": "3.27.0",
3
+ "version": "3.28.0",
4
4
  "description": "One CLI to rule them all. Unified orchestration layer for AI coding assistants. Auto-detection, auto-installation, auto-upgrade.",
5
5
  "type": "module",
6
6
  "bin": {