In this article
Jan Agent requires its own model and project configuration; Desktop generation does not establish file access or reviewed edits.
For a first local coding task in Jan Agent, connect the separate preview agent to a verified model endpoint and constrain the repository task before permitting changes. A good initial result is a reviewed edit with understood file ownership.
The concrete application boundary
The preview Agent adds file and command actions to a model conversation, so its first task needs a narrower contract than ordinary chat. Decide which directory is the project, which source file can change, and which existing check can be run. Desktop’s successful model answer establishes only generation. The Agent must still use the intended endpoint and operate in the intended project. Its approval behavior is also application configuration rather than a property of the model weights. The current permission documentation distinguishes an approval-oriented safe mode from operating system containment. An approved command can still reach whatever resources its process account is allowed to access (Jan Desktop documentation) (Jan Agent documentation).
A practical route
First confirm that the intended Desktop server can generate an answer with the selected local model. Then open the Agent in a disposable project directory and verify its own model configuration. Start by asking it to describe a specific source file. Review the proposed tools and approval settings before asking for a small edit (Jan Local API Server).
A worked example
Prepare a helper that formats a fictional status label. Ask the agent to explain the current fallback, then propose a clearer label for an unknown value. Inspect the resulting file diff and run the project’s relevant existing check yourself or through an explicitly reviewed action. Preserve the initial file so that the exact change remains independently inspectable.
| Check | Record |
|---|---|
| Scope | Only the formatting helper and its relevant existing check are in the initial task. |
| Endpoint | The Agent model configuration matches the separately verified local server. |
| Review | The changed fallback and check result are recorded beside the original source. |
Reading the failure correctly
Agent preview behavior should not be inferred from Desktop chat settings. An approval prompt controls an agent decision, while operating system permissions still determine what a launched command can access. If a tool fails, inspect that action and working directory before replacing an otherwise working local model.
What completes the check
Accept the workflow only when you can identify the endpoint, working directory, requested actions, and final diff. A successful explanation alone does not validate file editing; a generated claim that tests passed does not substitute for the actual check output. First verify that the working directory is disposable.
Related background: llama.cpp server: a local API from a GGUF model, VRAM for LLMs: why model size is only part of the calculation.