microsoft / microsoft/markitdown
Feature Request: Optional File Picker for Source and Output Paths
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 186k
- Forks
- 13.7k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 49
Description
Hi!
I'd like to propose an optional file-picker mode for MarkItDown.
Many users especially on Windows are not comfortable working with file paths in the terminal. especially if files are located on different drives.
Currently, users must specify paths explicitly:
markitdown path-to-file.pdf -o document.md
A possible enhancement would be to provide an optional flag that opens the system file picker to select the input file (and optionally the output location).
Examples:
# Select source file via file picker
markitdown --pick-file -o document.md
# Select both source and destination
markitdown --pick-file --pick-output
Alternatively, a single --gui flag could open dialogs for any missing paths.
This would remain completely optional and would not affect existing CLI workflows, scripts, automation, CI/CD usage, or headless environments.
I believe this could improve accessibility for less technical users (especially for vibe coders) while preserving the current command-line experience.
If this sounds useful, I'd be happy to work on an implementation and submit a pull request.
thanks for reading and have a great day!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the CLI argument handling for the existing input path and -o output path, then decide whether the proposed --pick-file/--pick-output or --gui behavior fits supported platforms. Verify that normal path-based use, scripts, CI/CD, and headless environments remain unaffected; done means optional source and destination selection works without changing existing workflows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100