Resolve symbolic links for configs for kiro-cli coding agent
已回答
Hi,
I have problem with configs for kiro-cli agent in intellij. I added custom agent to “chat ai” window with custom agent config. Configs are stored in .kiro folder and linked to central folder (symbolic links).
Context:
I have multiple projects/services so I decided to store ai-agents configs in central repo and share it across all projects. One of options to share configs (they have to be present in .kiro folder for each project) was to create symlinks in each project.
Problem:
The problem which I have is that this configs are not visible in kiro-cli agent in chat ai window. When I start kiro from terminal then everything works as expected. Is there any why to force intellij to use symbolic links in this case?
请先登录再写评论。
Hi Tomek Więcławek , could you please share some screenshots of what you saw in the Kiro-cli agent in chat AI window, and what's the result from terminal?
Hi, so here is a screen shot from my intellij where there are two agents: one is defined in standard file and second in another file referenced by symbolic link. And second agent is not visible in AI chat window:
From terminal both agents are available:
Hi Tomek Więcławek , thank you for sharing the screenshot. Seems like the Kiro Agent loaded in the AI Assistant cannot identify the symlink file, when it is loading the agent data.
Could you please help to collect the logs via Help | Collect Logs and Diagnostic Data, and the ACP log (https://www.jetbrains.com/help/ai-assistant/acp.html#collect-acp-logs).
Please upload the file to https://uploads.jetbrains.com/, and share the Upload ID with us. Thank you.
Hello,
I updated intellij to version 2025.3 and this solved the issue. For 2025.2 I uploaded the logs: Upload id: 2026_03_11_3cbNKQAuvSHPPfMoSByMfw (file: idea-logs-20260311-1204379453447461432578063.zip)
Thank you for sharing the log, I think this may be because the reload of ACP agent is not initialized properly. May be due to cache or other reasons. Good to know that updating to 2025.3 resolved the issue. Please help to monitor and if the issue occurs again, please kindly let us know.