AltimateAI / AltimateAI/altimate-code

Traces for current session gives an error

Open
#598 0 comments 0 reactions 0 assignees View on GitHub
bug from-cli user-feedback
Dominant language
TypeScript
Stars
811
Forks
134
Avg merge
3d 2h
Merged PRs (30d)
50

Description

When attempting to get trace for the current session, the UI shows "Trace not available yet – send a prompt first". This occurs even when the session has been active with multiple prompts and extensive tool calls (e.g., deep into a pipeline validation session with ClickHouse queries, code analysis, kubectl exec commands, git operations, and PR creation). The session clearly has many messages but the trace functionality does not recognize them.

---

### Metadata

| Field | Value |
|-------|-------|
| CLI Version | 0.0.0-feat/data-parity-skill-improvements-202603290103 |
| Platform | darwin |
| Architecture | arm64 |
| OS Release | 25.2.0 |
| Category | bug |
| Working Directory | altimateai |
| Session ID | ses_2bfbbb616ffeMGYU0Eu72jp5QN |

Image

Maybe it is a local dev issue - will verify

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.