@mention file path error

[scopewu]

What version of Kimi Code CLI is running?

kimi, version 1.30.0

Which open platform/subscription were you using?

/login

Which model were you using?

kimi 2.5

What platform is your computer?

Darwin 22.6.0 x86_64 i386

What issue are you seeing?

When using Kimi Web in the ~ directory, if you navigate to a page, create a new session, and enter @dir/file to reference a skill, Kimi cannot locate the file.

What steps can reproduce the bug?

When the working directory of the Kimi CLI differs from the directory where the session was created, @mention cannot find the selected file.

What is the expected behavior?

Additional information

No response

[he-yufeng]

Took a look at the code — I think the root cause is in web/api/sessions.py: when the user creates a session via Web UI without explicitly selecting a directory, the backend defaults to Path.home() instead of the startup directory (the CWD where kimi-cli was launched).

So if you start kimi-cli in ~/projects/myapp and create a new session without picking a directory, the session's work_dir is ~ instead of ~/projects/myapp. Then @src/main.py resolves against the wrong base path.

Quick fix would be defaulting to the startup directory instead of home. Happy to send a PR if that approach makes sense.

[bloodycoder]

Draft PR opened for review: #1845

Implemented:

• backend default work_dir for POST /api/sessions/ now prefers startup_dir
• fallback to HOME only when startup_dir is invalid or unavailable
• added fallback warning + structured info log fields (requested_work_dir, effective_work_dir, used_fallback_home)
• added API-level regression tests for session creation and path resolution behavior

Validation:

• pytest -q tests/web/test_sessions_create_default_workdir.py tests/web/test_open_in.py tests/web/test_static_cache_headers.py
• 11 passed, 2 skipped

If you prefer stricter fallback behavior (e.g. reject invalid startup_dir instead of HOME fallback), I can follow up with that change.