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
* fix: telemetry source tagging + duration guards
Add --source, --error-message, --failed-step flags to gstack-telemetry-log.
Source tagging (live vs test via GSTACK_TELEMETRY_SOURCE env) prevents E2E
tests from polluting production data. Duration guards cap unreasonable
values (>24h or negative → null).
Partial cherry-pick from garrytan/community-mode — non-breaking parts only.
Skips install_fingerprint rename (needs schema migration).
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
* feat: remove trigger guard + proactive opt-out prompt
Remove "MANUAL TRIGGER ONLY" injection from all skill descriptions. This
frees 59 chars per skill from the 1024-char Codex description budget and
lets skills auto-fire based on semantic matching.
Merge auto-fire control into the existing `proactive` setting — when false,
Claude won't auto-invoke skills or suggest them. Users are prompted once
about this preference (chains after the telemetry prompt, fires on second
skill run).
Also trims the root gstack description by removing the skill catalog
(already in the body), saving ~500 chars.
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
* chore: bump version and changelog (v0.11.16.0)
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
---------
Co-authored-by: Claude Opus 4.6 (1M context) <[email protected]>
-**Skill descriptions are now clean and readable.** Removed the ugly "MANUAL TRIGGER ONLY" prefix from every skill description that was wasting 58 characters and causing build errors for Codex integration.
8
+
-**You can now opt out of proactive skill suggestions.** The first time you run any gstack skill, you'll be asked whether you want gstack to suggest skills during your workflow. If you prefer to invoke skills manually, just say no — it's saved as a global setting. You can change your mind anytime with `gstack-config set proactive true/false`.
9
+
10
+
### Fixed
11
+
12
+
-**Telemetry source tagging no longer crashes.** Fixed duration guards and source field validation in the telemetry logger so it handles edge cases cleanly instead of erroring.
13
+
3
14
## [0.11.16.1] - 2026-03-24 — Installation ID Privacy Fix
If `PROACTIVE` is `"false"`, do not proactively suggest gstack skills — only invoke
60
-
them when the user explicitly asks. The user opted out of proactive suggestions.
52
+
If `PROACTIVE` is `"false"`, do not proactively suggest gstack skills AND do not
53
+
auto-invoke skills based on conversation context. Only run skills the user explicitly
54
+
types (e.g., /qa, /ship). If you would have auto-invoked a skill, instead briefly say:
55
+
"I think /skillname might help here — want me to run it?" and wait for confirmation.
56
+
The user opted out of proactive behavior.
61
57
62
58
If output shows `UPGRADE_AVAILABLE <old> <new>`: read `~/.claude/skills/gstack/gstack-upgrade/SKILL.md` and follow the "Inline upgrade flow" (auto-upgrade if configured, otherwise AskUserQuestion with 4 options, write snooze state if declined). If `JUST_UPGRADED <from> <to>`: tell user "Running gstack v{to} (just updated!)" and continue.
This only happens once. If `TEL_PROMPTED` is `yes`, skip this entirely.
108
104
105
+
If `PROACTIVE_PROMPTED` is `no` AND `TEL_PROMPTED` is `yes`: After telemetry is handled,
106
+
ask the user about proactive behavior. Use AskUserQuestion:
107
+
108
+
> gstack can proactively figure out when you might need a skill while you work —
109
+
> like suggesting /qa when you say "does this work?" or /investigate when you hit
110
+
> a bug. We recommend keeping this on — it speeds up every part of your workflow.
111
+
112
+
Options:
113
+
- A) Keep it on (recommended)
114
+
- B) Turn it off — I'll type /commands myself
115
+
116
+
If A: run `~/.claude/skills/gstack/bin/gstack-config set proactive true`
117
+
If B: run `~/.claude/skills/gstack/bin/gstack-config set proactive false`
118
+
119
+
Always run:
120
+
```bash
121
+
touch ~/.gstack/.proactive-prompted
122
+
```
123
+
124
+
This only happens once. If `PROACTIVE_PROMPTED` is `yes`, skip this entirely.
125
+
109
126
## Contributor Mode
110
127
111
128
If `_CONTRIB` is `true`: you are in **contributor mode**. At the end of each major workflow step, rate your gstack experience 0-10. If not a 10 and there's an actionable bug or improvement — file a field report.
If `PROACTIVE` is `"false"`, do not proactively suggest gstack skills — only invoke
61
-
them when the user explicitly asks. The user opted out of proactive suggestions.
61
+
If `PROACTIVE` is `"false"`, do not proactively suggest gstack skills AND do not
62
+
auto-invoke skills based on conversation context. Only run skills the user explicitly
63
+
types (e.g., /qa, /ship). If you would have auto-invoked a skill, instead briefly say:
64
+
"I think /skillname might help here — want me to run it?" and wait for confirmation.
65
+
The user opted out of proactive behavior.
62
66
63
67
If output shows `UPGRADE_AVAILABLE <old> <new>`: read `~/.claude/skills/gstack/gstack-upgrade/SKILL.md` and follow the "Inline upgrade flow" (auto-upgrade if configured, otherwise AskUserQuestion with 4 options, write snooze state if declined). If `JUST_UPGRADED <from> <to>`: tell user "Running gstack v{to} (just updated!)" and continue.
If `PROACTIVE` is `"false"`, do not proactively suggest gstack skills — only invoke
54
-
them when the user explicitly asks. The user opted out of proactive suggestions.
54
+
If `PROACTIVE` is `"false"`, do not proactively suggest gstack skills AND do not
55
+
auto-invoke skills based on conversation context. Only run skills the user explicitly
56
+
types (e.g., /qa, /ship). If you would have auto-invoked a skill, instead briefly say:
57
+
"I think /skillname might help here — want me to run it?" and wait for confirmation.
58
+
The user opted out of proactive behavior.
55
59
56
60
If output shows `UPGRADE_AVAILABLE <old> <new>`: read `~/.claude/skills/gstack/gstack-upgrade/SKILL.md` and follow the "Inline upgrade flow" (auto-upgrade if configured, otherwise AskUserQuestion with 4 options, write snooze state if declined). If `JUST_UPGRADED <from> <to>`: tell user "Running gstack v{to} (just updated!)" and continue.
This only happens once. If `TEL_PROMPTED` is `yes`, skip this entirely.
102
106
107
+
If `PROACTIVE_PROMPTED` is `no` AND `TEL_PROMPTED` is `yes`: After telemetry is handled,
108
+
ask the user about proactive behavior. Use AskUserQuestion:
109
+
110
+
> gstack can proactively figure out when you might need a skill while you work —
111
+
> like suggesting /qa when you say "does this work?" or /investigate when you hit
112
+
> a bug. We recommend keeping this on — it speeds up every part of your workflow.
113
+
114
+
Options:
115
+
- A) Keep it on (recommended)
116
+
- B) Turn it off — I'll type /commands myself
117
+
118
+
If A: run `~/.claude/skills/gstack/bin/gstack-config set proactive true`
119
+
If B: run `~/.claude/skills/gstack/bin/gstack-config set proactive false`
120
+
121
+
Always run:
122
+
```bash
123
+
touch ~/.gstack/.proactive-prompted
124
+
```
125
+
126
+
This only happens once. If `PROACTIVE_PROMPTED` is `yes`, skip this entirely.
127
+
103
128
## Contributor Mode
104
129
105
130
If `_CONTRIB` is `true`: you are in **contributor mode**. At the end of each major workflow step, rate your gstack experience 0-10. If not a 10 and there's an actionable bug or improvement — file a field report.
If `PROACTIVE` is `"false"`, do not proactively suggest gstack skills — only invoke
54
-
them when the user explicitly asks. The user opted out of proactive suggestions.
54
+
If `PROACTIVE` is `"false"`, do not proactively suggest gstack skills AND do not
55
+
auto-invoke skills based on conversation context. Only run skills the user explicitly
56
+
types (e.g., /qa, /ship). If you would have auto-invoked a skill, instead briefly say:
57
+
"I think /skillname might help here — want me to run it?" and wait for confirmation.
58
+
The user opted out of proactive behavior.
55
59
56
60
If output shows `UPGRADE_AVAILABLE <old> <new>`: read `~/.claude/skills/gstack/gstack-upgrade/SKILL.md` and follow the "Inline upgrade flow" (auto-upgrade if configured, otherwise AskUserQuestion with 4 options, write snooze state if declined). If `JUST_UPGRADED <from> <to>`: tell user "Running gstack v{to} (just updated!)" and continue.
This only happens once. If `TEL_PROMPTED` is `yes`, skip this entirely.
102
106
107
+
If `PROACTIVE_PROMPTED` is `no` AND `TEL_PROMPTED` is `yes`: After telemetry is handled,
108
+
ask the user about proactive behavior. Use AskUserQuestion:
109
+
110
+
> gstack can proactively figure out when you might need a skill while you work —
111
+
> like suggesting /qa when you say "does this work?" or /investigate when you hit
112
+
> a bug. We recommend keeping this on — it speeds up every part of your workflow.
113
+
114
+
Options:
115
+
- A) Keep it on (recommended)
116
+
- B) Turn it off — I'll type /commands myself
117
+
118
+
If A: run `~/.claude/skills/gstack/bin/gstack-config set proactive true`
119
+
If B: run `~/.claude/skills/gstack/bin/gstack-config set proactive false`
120
+
121
+
Always run:
122
+
```bash
123
+
touch ~/.gstack/.proactive-prompted
124
+
```
125
+
126
+
This only happens once. If `PROACTIVE_PROMPTED` is `yes`, skip this entirely.
127
+
103
128
## Contributor Mode
104
129
105
130
If `_CONTRIB` is `true`: you are in **contributor mode**. At the end of each major workflow step, rate your gstack experience 0-10. If not a 10 and there's an actionable bug or improvement — file a field report.
0 commit comments