Workspace skill sync failures are invisible to the user
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- cli
Research direction
Start with packages/opencode/src/session/prompt.ts:392-395 and the log.warn sites in packages/opencode/src/altimate/workspace/skill-sync.ts; trace how workspace skill-sync failures currently propagate and compare the release's MCP status diagnostics. Done means a user can distinguish sync failure from missing skills through a user-visible status surface, with the beta notes limitation called out if applicable.
Written by the indexing model from the issue text.
Description
Deferred from the v0.10.0 release review. Flagged by the end-user reviewer as the release's biggest usability gap.
Every failure path in workspace skill sync is log.warn only — no toast, no session message, nothing in any status command. See packages/opencode/src/session/prompt.ts:392-395 and roughly a dozen log.warn sites in packages/opencode/src/altimate/workspace/skill-sync.ts.
So a user who links a workspace expecting a custom skill has no way to distinguish "it failed to sync" from "it isn't there yet" without digging through CLI logs.
The contrast within this same release is stark: the MCP work built exactly this kind of surfaced diagnostic (mcp status, real connection errors, config-drift reporting). Skills got no equivalent.
Needs a small user-visible status surface, not a wording change — which is why it was not folded into the release PR.
Worth calling out as a known limitation in the beta notes so pilot users know to check logs rather than assume no skills exist.
- Dominant language
- TypeScript
- Stars
- 813
- Forks
- 134
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 67
Contributor guide
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 AltimateAI/altimate-code
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
AltimateAI/altimate-code#1359 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
AltimateAI/altimate-code#1323 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
AltimateAI/altimate-code#1288 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
AltimateAI/altimate-code#1285 ·
-
privacy: Altimate Base consent dialog no longer discloses persistent per-installation identifier Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
AltimateAI/altimate-code#1284 ·
All issues in AltimateAI/altimate-code
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
IBM/node-sdk-core#373 ·
-
e2e-failure ready-to-code
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
chore
Difficulty 2/5 1-3 hours Newbie friendliness 88/100