Two features that need both repos since ualtinok owns both.
1. Tool-output search
Right now aft_search indexes source files. ctx_search indexes messages, but not the raw stdout/stderr from bash commands. If a path or identifier only appeared in command output, neither tool finds it.
Needs both repos since MC owns the message FTS and AFT generates the output. Rough sketch:
- AFT tags bash output with a content hash before compression
- MC indexes those tagged blocks alongside message text so ctx_search finds them
- Or AFT maintains its own output index and aft_search includes it
Alternative: just index tool results as regular messages in MC. Might already work if tool_result parts are included in the text field the FTS processes. Needs investigation.
2. Memory-code linking
No way to say "show me code related to memory entry X" or "link this file to memory about it". Two cortexkit tools that dont talk to each other.
MC stores memories with file paths in the content text. AFT can open those files. But theres no structured link: you cant query "which memories mention this file" or "open the file referenced by memory #42".
Fix: MC embeds file paths as structured references (not just text), and AFT accepts memory IDs to resolve the referenced file.
Two features that need both repos since ualtinok owns both.
1. Tool-output search
Right now aft_search indexes source files. ctx_search indexes messages, but not the raw stdout/stderr from bash commands. If a path or identifier only appeared in command output, neither tool finds it.
Needs both repos since MC owns the message FTS and AFT generates the output. Rough sketch:
Alternative: just index tool results as regular messages in MC. Might already work if tool_result parts are included in the text field the FTS processes. Needs investigation.
2. Memory-code linking
No way to say "show me code related to memory entry X" or "link this file to memory about it". Two cortexkit tools that dont talk to each other.
MC stores memories with file paths in the content text. AFT can open those files. But theres no structured link: you cant query "which memories mention this file" or "open the file referenced by memory #42".
Fix: MC embeds file paths as structured references (not just text), and AFT accepts memory IDs to resolve the referenced file.