serve: persist session traces across container restarts (Dockerfile VOLUME / XDG guidance)

Open
#915 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
docker
Domain
documentation, infrastructure

Research direction

Read the deploy/Docker documentation and packages/opencode/Dockerfile first, then trace how altimate serve uses $XDG_DATA_HOME/altimate-code/traces/ and the tracing.dir override. Define the recommended volume mount and resolve whether VOLUME or XDG_DATA_HOME changes belong in the Dockerfile; done means the persistence guidance and agreed container behavior are documented and consistent.

Written by the indexing model from the issue text.

Description

Found during the v0.8.6 release review (Chaos/k8s persona). Deferred because it's a deployment/Dockerfile behavior change that needs design thought, not a quick fix.

Now that altimate serve writes session traces (#886), traces land under $XDG_DATA_HOME/altimate-code/traces/ (default ~/.local/share/altimate-code/traces/). In a container this is the ephemeral filesystem — a pod restart / rolling update / OOMKill silently drops the entire trace history.

Proposed:

  • Document a recommended volume mount for the trace dir in the deploy/Docker docs.
  • Consider VOLUME/ENV XDG_DATA_HOME in packages/opencode/Dockerfile (carefully — it changes default paths).
  • Reference tracing.dir config as the override knob.
Dominant language
TypeScript
Stars
813
Forks
134
Avg merge
2d 5h
Merged PRs (30d)
62

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AltimateAI/altimate-code

All issues in AltimateAI/altimate-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.