@generate mode doesn't know the name of the pinned context file

[kgilpin]

When using the @generate command, Navie doesn't know the name of the pinned file.

You can see how, in this screenshot, I have pinned a context file called "official.py".

Then I've asked a typical code generation question. Navie outputs code snippets referring to `/path/to/your/script.py' rather than the pinned file.

It will also propose (correct) changes to the wrong file name:

See also

• @generate mode doesn't recognize the file name of the code selection #2187

--

• When the context is provided to the navie package, it should include the file names and file contents.
• @generate mode should observe and use the file names provided in the pinned context.
• It may be useful to add some type information to the context / aka codeSelection. It can be an arbitrary blob, but in many cases, such as when the user is pinning context, it has defined structure.

[github-actions]

Title: Update Navie to Recognize and Use Pinned Context File Names in @generate Mode

Problem: When using the @generate command, Navie has trouble identifying the actual names of pinned context files. It ends up using placeholders like /path/to/your/script.py instead of utilizing the actual file names provided by the user, such as "official.py". This results in confusing and potentially incorrect code generation output.

Analysis: The root cause of this issue seems to be the lack of a direct mapping or recognition mechanism within Navie's @generate mode that ties pinned file contexts to their respective names. When users pin files for context, Navie should be able to link the content with its file name and correctly suggest changes or generate code pertaining to that file. Upon inspecting the current context handling, Navie appears to treat pinned context as generic text blobs without any associated metadata, such as file names.

To resolve this, the system requires enhancements in how contexts are processed and used. Adjustments to data structures or handling logic that allow inclusion and recognition of metadata, like filenames, are necessary. This kind of structured information will enable Navie to correlate the specific content, intended file references, and context needed for precise code generation.

Proposed Changes:

1. Navie Context Handling Improvements:

   • Update the context processing module in the navie package to not only receive but also store metadata alongside content. Specifically, ensure that file names and paths are included when contexts are pinned.

2. Enhance @generate Logic:

   • Modify the generate-agent.ts file to incorporate logic that parses and uses the enhanced context structure. When executing the @generate command, ensure it checks for file name metadata within the provided contexts and uses this information to populate file paths correctly in code snippets and proposals.

3. Agent Integration:

   • Update the integration within the Agent class definitions of plan-agent and generate-agent to use the enhanced context structure, ensuring it correctly identifies file name metadata during interaction events.

4. Update the Classification Service:

   • Adjust the classification-service.ts to recognize when the user pins files, and ensure this is communicated back to the relevant processing functions to maintain integrity between the context and executions by the agents.

5. Documentation Updates:

   • Amend sections within the user guides found in using-navie.md to appropriately reflect the functionality of recognized pinned context files. Include examples to demonstrate the process and expected outcomes with accurate file names.

This approach will align the @generate functionality with user expectations and enhance usability, ensuring the code generation process accurately reflects user-pinned contexts and avoids erroneous file references.

[dustinbyrne]

In the first image, no code snippets are found. The instructions referencing a file are included as part of the code snippet prompt description, which will not be included in the absence of code snippets:
https://github.com/getappmap/appmap-js/blob/main/packages/navie/src/services/apply-context-service.ts#L103-L110