The troubleshooting page was deleted earlier in this PR with a redirect
to the wasteland index, but several inline links still pointed at the
old path. Lychee link-checker treats those as broken because it
validates files on disk rather than honoring redirects. Repoint them at
/docs/code-with-ai/gastown/wasteland directly.
Defining FitOnResize inside the parent render gave it a new component
identity on every parent render, forcing React to unmount/remount it
and tear down the ResizeObserver each time. Hoist it to module scope
and pass useReactFlow in as a prop. Also drop the unused instanceRef.
Update the mobile apps page to reflect that the Android app is now available on Google Play and provide a link for installation.
Added detailed information about mobile app capabilities, including session management, KiloClaw chat, and Cloud Agent spawning. Included new screenshots to illustrate the mobile interface and added a section for the iOS app waitlist.
* fix: catch EEXIST from recursive mkdir on Windows
fs.mkdir with { recursive: true } can still throw EEXIST on Windows
when the target directory is backed by an NTFS reparse point (OneDrive),
a directory junction, or a WSL-served path. libuv's recursive walk
doesn't treat these as regular directories, so mkdir with recursive:true
attempts to create an already-existing path segment and fails.
This adds a defensive EEXIST catch at both directory-creation origins:
- AppFileSystem.ensureDir / writeWithDirs (snapshots, config, plans)
- Encoding.write (all tool writes and edits)
No functional change on Linux/macOS where EEXIST is never thrown from
recursive mkdir.
Fixes#9618, #9755
* fix: remove extra arg from mkdirSafe call, add unit tests
* docs(kilo-docs): update auto-generated source links
Add 2 new GitHub issue references (9618, 9755) from encoding.ts
and update URL count from 84 to 86.
---------
Co-authored-by: nimgrim <nimgrim@users.noreply.github.com>
Co-authored-by: Imanol Maiztegui <imanol.mzd@gmail.com>
- Add DeepSeek to the Standard API keys list on the BYOK page (Kilo-Org/cloud#3167)
- Update auto-model-tiers architecture doc to reflect the new default of kilo-auto/free for all new users (Kilo-Org/kilocode#10151)
This flag currently does nothing. Presumably, it was recently added by
OpenCode upstream, but since Kilo already has the `--auto` flag, the
code that would handle `--dangerously-skip-permissions` is wired into
`--auto` instead.
Removing this useless flag avoids confusion for users.
kilo-maintainer[bot]