The issue with the file path generated by the Agent
- Dominant language
- TypeScript
- Stars
- 156k
- Forks
- 24.6k
- Avg merge
- 22h 9m
- Merged PRs (30d)
- 610
Description
### Self Checks
- [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542).
- [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones.
- [x] I confirm that I am using English to submit this report, otherwise it will be closed.
- [x] Please do not modify this template :) and fill in all the required fields.
### 1. Is this request related to a challenge you're experiencing? Tell me about your story.
I am testing the file processing capability of the Agent. However, when the Agent finished processing or generating the file, the file path provided to me was within the Docker container, which couldn't be directly given in the conversation interface. This was not very convenient.
### 2. Additional context or comments
If a workspace file browsing window could be added to the chat interface, or if the Agent could directly display the processed files in the conversation area, this would be much more convenient.
### 3. Can you help us with this feature?
- [x] I am interested in contributing to this feature.
Contributor guide
Research direction
No files, tests, or entry points are identified in the issue. Clarify whether the goal is workspace file browsing or inline file display, then define the expected chat behavior and accessible file path before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- ai, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100