steipete/eightctl
Vedi su GitHub`metrics insights` fails: API returns 404 for `/v1/users/{id}/insights`
Open
#42 aperta il 13 lug 2026
P2clawsweeper:current-main-reproclawsweeper:fix-shape-clearclawsweeper:queueable-fixgood first issueimpact:ux-frictionissue-rating: 🦀 challenger crabno-stale
Metriche repository
- Star
- (80 star)
- Metriche merge PR
- (Metriche PR in attesa)
Descrizione
What happens
$ eightctl metrics insights
Error: api GET https://client-api.8slp.net/v1/users/<user-id>/insights: <!DOCTYPE html>
...
<pre>Cannot GET /v1/users/<user-id>/insights</pre>
The Cannot GET HTML body is the server's own 404 page, so this isn't an auth or client-side issue — the route doesn't exist on client-api.8slp.net (removed or never shipped).
What works
Same binary, same credentials:
eightctl metrics trends --from ... --to ...— works fineeightctl metrics intervals --id <sessionID>— works fine
So only the Insights() call in internal/client/metrics.go (/users/{id}/insights) is affected.
Version
eightctl@v0.0.0-20260713021800-e05b8da853b9 (installed via go install ...@latest)
Suggestion
Either drop the subcommand, or point it at whatever endpoint currently serves insights data — the trends response already includes most of the insight-style fields (performanceWindows, chronotype, socialJetlag), so it may have been folded into /trends?model-version=v2.