@Meh10t have you confirmed that the Kotlin download fix in b26acaa works, i.e. that this not only fixes the download but the LS is also operational?
If so, we should prioritise bringing this to main.

@Meh10t have you confirmed that the Kotlin download fix in b26acaa works, i.e. that this not only fixes the download but the LS is also operational? If so, we should prioritise bringing this to main.

You're right — the Kotlin LSP change was outside the scope of #1055.

I’ve removed that commit and reverted the branch to focus only on the frontmatter tools implementation.

Apologies for the confusion.

@opcode81 Hi,

I just wanted to clarify the current situation regarding issue #1055.

I’m a bit confused about whether this issue is still assigned to me and if I should continue working on it. I opened PR #1065 and started implementing the nested memory paths and topic filtering, and I was planning to continue with the opt-in frontmatter tools (MemoryAddFrontmatterTool and MemoryGetFrontmatterTool) as discussed.

Could you please confirm if I should proceed with the full implementation, or if the direction has changed?

I’m happy to adapt my work to match the maintainers’ expectations.

Thanks!

Hi @Meh10t . As we discussed, the grouping has now been implemented but the frontmatter part has not and is assigned to you :)

The issue was closed by accident, I hadn't noticed that the PR was scheduled to close it. Sry about that