Skip to content

llama-atmosphere-agent: document the 5.2.0 release flow, drop -Dllama.version from the commands - #445

Merged
bernardladenthin merged 1 commit into
mainfrom
claude/jolly-noether-jlebto
Sep 21, 2026
Merged

bernardladenthin merged 1 commit into
mainfrom
claude/jolly-noether-jlebto

Conversation

@bernardladenthin

Copy link
Copy Markdown
Owner

Summary

  • Follow-up to Add llama-atmosphere-agent: local JVM coding agent with Atmosphere #444: the agent docs are now written for the 5.2.0 release (as if released), so every documented command runs with no -D at all. llama-atmosphere-agent/pom.xml sets llama.version to 5.2.0; CI keeps overriding it with the reactor version it just installed, so a not-yet-published default cannot break CI. The Sonatype snapshot repository stays in the pom, but is only consulted for a -Dllama.version=<x>-SNAPSHOT override.
  • Both READMEs (root "Local coding agent" section + llama-atmosphere-agent/README.md) show the flow a user actually follows: java-llama.cpp already running from the release fat jar (java -jar llama-5.2.0-jar-with-dependencies.jar -m … --jinja --port 8080), then the agent from the llama-atmosphere-agent/ folder (mvn -q compile exec:java -Dexec.args="--base-url http://127.0.0.1:8080/v1 --workspace … --allow-shell"), the you> REPL (/ tool lines, /clear, /exit), the one-shot --prompt variant, the --api-key note, and the in-process --model alternative.
  • CLAUDE.md's version-bump note now says to bump the pom's release version and the fat-jar filename in both READMEs at release time, and to use -Dllama.version=<x>-SNAPSHOT before a release.

Docs and pom only; no code change. Consistency check across README / CLAUDE.md / CHANGELOG / TODO / the agent README found no other drift.

Test plan

  • Affected unit / integration tests pass locally — mvn clean verify -Dllama.version=5.2.0-SNAPSHOT in llama-atmosphere-agent/ against the locally installed core: 23 tests, 20 run green, 3 model-backed self-skip
  • The agent still compiles against the released core (-Dllama.version=5.1.0), so the main code needs nothing beyond a release
  • CI is green on this branch
  • Docs / CHANGELOG updated where applicable (this PR is the docs update)

Related issues / PRs

Refs #444

Checklist

  • I have read CONTRIBUTING.md and CODE_OF_CONDUCT.md
  • My commits follow Conventional Commits
  • No security-sensitive changes (if there are, I have notified the maintainer privately per SECURITY.md)

🤖 Generated with Claude Code

https://claude.ai/code/session_01UVwj2UuMPybiK1bHyG9toH


Generated by Claude Code

….version from the commands

The pom's llama.version now names the release the READMEs describe (5.2.0,
written as if released), so the documented commands run with no -D at all.
Both READMEs show the two-step flow a user actually follows: java-llama.cpp
already running from the release fat jar with --jinja, then the agent from
the llama-atmosphere-agent/ folder (REPL with you>, /clear, /exit; a one-shot
--prompt variant; the in-process --model alternative). CLAUDE.md's bump note
now says to bump the pom version and the fat-jar filename at release time,
and to use -Dllama.version=<x>-SNAPSHOT before a release (the snapshot
repository stays in the pom for that). CI is unaffected: it keeps overriding
llama.version with the reactor version it just installed.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UVwj2UuMPybiK1bHyG9toH
@bernardladenthin
bernardladenthin merged commit 05b0a32 into main Sep 21, 2026
8 of 14 checks passed
@bernardladenthin
bernardladenthin deleted the claude/jolly-noether-jlebto branch September 21, 2026 13:00
@sonarqubecloud

Copy link
Copy Markdown

This branch had an error being deployed

1 failed deployment
maven-central 95a078cf Deployed Sep 21, 2026 by bernardladenthin via Verify GPG signing key (no secrets printed) #974
startgate 95a078cf Deployed Sep 21, 2026 by bernardladenthin via Start gate (abort window) #974
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants