Skip to content

llama-atmosphere-agent: document the from-scratch workflow - #453

Merged
bernardladenthin merged 1 commit into
mainfrom
agent-readme-getting-started
Sep 21, 2026
Merged

bernardladenthin merged 1 commit into
mainfrom
agent-readme-getting-started

Conversation

@bernardladenthin

Copy link
Copy Markdown
Owner

Why

The agent README assumed the reader already had the folder, a model and — for mode A — a fat jar. A user on a fresh machine with only JDK + Maven had to guess those steps.

What

llama-atmosphere-agent/README.md

  1. Getting the folder: git clone --depth 1 … + cd java-llama.cpp/llama-atmosphere-agent (or the GitHub ZIP); the folder is self-contained, .mvn/jvm.config included.
  2. Getting a model: a curl download of Qwen3-4B-Instruct-2507 Q4_K_M (unsloth GGUF repo — the official Qwen repo returns 401 without login). All examples now use models/Qwen3-4B-… instead of a mix of model names.
  3. Fat jar for mode A: they are GitHub release assets; llama-<v>-jar-with-dependencies.jar is CPU (+ Metal), llama-<v>-all-<os>-<arch>-jar-with-dependencies.jar carries every GPU backend and uses the first whose runtime loads (-Dnet.ladenthin.llama.backend=… forces one).
  4. Windows: a full PowerShell start command, not just the quoting hint.
  5. Warning box: --allow-shell runs any command with the user's rights, without asking.
  6. Limitations: one in-process agent per machine (fixed temp-dir native library name — on Windows the second JVM fails with Failed to delete old native lib / No native library found; shared GPU memory); run one server and point several agents at it instead.

Root README.md: the same short path (clone, model, run, warning, PowerShell/GPU hint), links to the agent README.

.gitignore: llama-atmosphere-agent/models/*.gguf — the README downloads the model there, and the existing models/*.gguf rule only covers the root.

Verified

Windows 11: the documented PowerShell command (--model models\Qwen3-4B-Instruct-2507-Q4_K_M.gguf …, CPU jar) runs, calls ls and answers; the model copied into models/ does not show up in git status. Model URL checked (HTTP 200).

🤖 Generated with Claude Code

https://claude.ai/code/session_01E2h8gXyyE5UeimkL9vQv9G

The agent README assumed the reader already had the folder, a model and (for
mode A) a fat jar. It now walks a new user through it:

- "Getting started from scratch": git clone, a curl download of a tool-capable
  model (Qwen3-4B-Instruct-2507 from unsloth's GGUF repo), the start command for
  Linux/macOS and for Windows PowerShell, and the GPU classifier as an optional
  step. Examples use models/Qwen3-4B-... throughout instead of mixed model names.
- Mode A says where the fat jars come from (GitHub release assets) and that the
  all-<os>-<arch> jars pick a GPU backend themselves (net.ladenthin.llama.backend
  forces one).
- A warning box: with --allow-shell the model runs any command with the user's
  rights, without asking.
- Limitations: one in-process agent per machine (fixed temp-dir native library
  name on Windows, shared GPU memory); several agents should share one server.
- Root README: the same short path (clone, model, run, warning).
- .gitignore: llama-atmosphere-agent/models/*.gguf, where the README downloads the
  model (the existing models/*.gguf rule only covers the root).

Verified on Windows: the documented PowerShell command with the relative
models\ path runs on the CPU jar, calls a tool and answers; the copied model is
not shown by git status.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E2h8gXyyE5UeimkL9vQv9G
@bernardladenthin
bernardladenthin merged commit e3e2161 into main Sep 21, 2026
9 of 79 checks passed
@bernardladenthin
bernardladenthin deleted the agent-readme-getting-started branch September 21, 2026 22:15

This branch had an error being deployed

1 failed deployment
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.

1 participant