File System Tools: Race Safety & Operational Hardening

Atomic Writes (Safe File Saving)

• When Kader creates a new file or edits an existing one, it now writes the content to a temporary file first, and only replaces the original file once everything is written and verified successfully.
• The temporary file is created in the same directory as the file being written, with .kader-tmp added to the end of the filename. For example, if Kader is editing config.json, the temp file will be config.json.kader-tmp in the same folder. Once the write is complete and verified, the temp file replaces the original and the .kader-tmp file disappears. If the write fails, the temp file is automatically cleaned up.
• What this means for you: You will never see a half-written or corrupted file, even if something goes wrong in the middle of a write (such as a crash, power loss, or disk error). Your file is either fully updated or left completely unchanged — no in-between state.

Freshness Tokens (Avoid Overwriting Others' Changes)

• When Kader reads a file, it can optionally note the file's "last modified" timestamp. When it later tries to edit that same file, it can check whether the file has been changed by someone else in the meantime.
• What this means for you: If another person, tool, or process modified the file since Kader last read it, Kader will detect the mismatch and refuse to overwrite the file. Instead, it alerts you that the file was changed, so you can review the latest version first. This prevents accidentally clobbering someone else's work.

File Locking (Preventing Concurrent Edit Conflicts)

• When Kader is editing a file, it briefly locks that file so that if another agent or process tries to edit the same file at the exact same time, it will wait until the first edit is finished.
• What this means for you: Multiple agents, tools, or processes can work safely in the same project without stepping on each other's toes. The lock is automatically removed after the edit is complete — there are no leftover lock files to clean up. On systems that do not support file locking, Kader simply skips this step gracefully, so nothing breaks.

v2.14.2

Merge pull request #110 from Kader-AI-hub/core-cli/commands

add sessions command to docs

v2.14.1

Merge pull request #108 from Kader-AI-hub/project-urls

add project URLs

kader core framework CLI

Merge pull request #107 from Kader-AI-hub/feature/core-cli

Feature/core cli

subagents

Merge pull request #106 from Kader-AI-hub/release/v2.13.0

upgrade kader to v2.13.0

CLI Connect Command

Merge pull request #100 from Kader-AI-hub/cli/provider-connect

Cli/provider connect

Opencode Go Provider Support

Merge pull request #99 from Kader-AI-hub/provider/opencode-go

Provider/opencode go

v2.11.2

Merge pull request #98 from Kader-AI-hub/refactor/llmfactory

Refactor/llmfactory

v2.11.1

Merge pull request #97 from Kader-AI-hub/refactor/remove-indexing-tools

Refactor/remove indexing tools

Custom Tools

Merge pull request #94 from Kader-AI-hub/feature/custom-tools

Feature/custom tools