marker-pdf-agent 1.1.2

Document conversion agent that watches folders, converts files with marker-pdf, and routes Markdown outputs.

marker-pdf-agent

A small document-conversion agent for turning PDFs and other supported documents into Markdown with marker-pdf. It watches a folder, converts files dropped into incoming/, and saves the original plus the converted Markdown or asset zip under converted/<category>/.

Use it as a foreground command, an optional status-bar app, or a user-level background service. Folder routing is local by default, with optional Ollama-assisted category selection when you explicitly enable it.

Install

Install from PyPI:

pip install marker-pdf-agent

Install the optional desktop dependencies if you want the status-bar app:

pip install "marker-pdf-agent[gui]"

Python 3.10 or newer is required. The core marker-pdf dependency is installed automatically.

ollama is optional and is not started or queried unless you explicitly pass --ollama-model. Without that flag, converted files go to converted/uncategorized.

Run

Start the agent from the folder you want it to manage:

marker-pdf-agent

Or choose a folder explicitly:

marker-pdf-agent --root /path/to/folder

The agent creates the folders it needs on startup. Move documents into incoming/, wait for conversion, then collect the output from converted/uncategorized/ unless you enabled Ollama routing.

Status-Bar App

The status-bar app is for foreground use. It shows the current state, queue size, and monitored folders, and it can open the incoming/ and converted/ folders for you. On macOS it runs as a menu-bar app rather than showing a Dock icon.

Launch it with either command:

marker-pdf-agent tray
marker-pdf-agent tray --root /path/to/folder

To create a clickable launcher in the managed folder, run:

marker-pdf-agent install-launcher --root /path/to/folder

The installer writes the native launcher format for the current operating system: a .app bundle on macOS, a .desktop file on Linux, or a .cmd launcher on Windows. The launcher starts the status-bar app for that folder using the Python environment that created it, so it does not depend on your desktop session inheriting the same PATH as your terminal. Use --launcher-name "Marker PDF Agent" to choose a different display name. On macOS, launcher output is appended to .marker-pdf-agent/launcher.log under the managed folder. If macOS blocks a launcher from reading a virtual environment under a protected folder such as Downloads, Desktop, or Documents, move the managed folder or environment outside that protected location, or grant the launcher Full Disk Access, then reinstall the launcher.

Click the status-bar icon to open the menu. From there you can add or remove monitored folders, choose an Ollama routing model, refresh the installed Ollama model list, and quit cleanly. Detailed progress and routing messages are printed to the terminal that launched the app.

Use the Ollama routing submenu to choose Disabled or one of the installed Ollama models. Choose Refresh models to query ollama list in the background; the app does not query Ollama just from opening the tray menu. The selected model is persisted with the tray config and applies to all monitored folders.

Monitored folders and the selected Ollama model are persisted in ~/.marker-pdf-agent/config.json by default. Use --config /path/to/config.json to choose a different config file. The --root folder passed at launch is added to that file automatically, and folders or model settings changed from the status-bar app update the same file.

Multiple monitored folders share one queue, so only one conversion runs at a time. Removing a monitored folder stops future scans and drops pending queued jobs for that folder.

By default the worker creates and uses these folders:

• incoming/ - move documents here for conversion
• .marker-pdf-agent/processing/ - temporary in-progress files
• .marker-pdf-agent/failed/ - source files that failed conversion
• converted/<category>/ - original documents plus final Markdown or zip artifacts

If conversion produces only Markdown, the final artifact is a .md file. If marker emits images or other assets, the final artifact is a .zip containing the Markdown plus assets. The original document is moved into the same category folder as the converted artifact.

If a conversion fails, times out, or is interrupted during shutdown, the source document is moved to .marker-pdf-agent/failed/. If the worker starts and finds leftover files in .marker-pdf-agent/processing/ from a previous interrupted run, it moves them to .marker-pdf-agent/failed/ so they are visible for manual retry.

Options

marker-pdf-agent run \
  --root /path/to/folder \
  --incoming incoming \
  --converted converted \
  --marker-command marker_single \
  --marker-timeout 1800 \
  --ollama-model llama3.1

Useful flags:

• --root: manage a folder other than the current working directory
• --config: choose the persisted status-bar app config file, defaults to ~/.marker-pdf-agent/config.json
• --incoming: choose the watched subfolder
• --converted: choose the output subfolder
• --marker-command: choose the marker-pdf executable, defaults to marker_single
• --marker-timeout: maximum seconds to allow one conversion before moving it to failed, defaults to 1800
• --ollama-model: enable AI folder routing with a specific installed Ollama model
• --no-ollama: disable AI folder routing; this is the default unless --ollama-model is set
• --launcher-name: choose the display name when using install-launcher, defaults to Marker PDF Agent

Background Service

Install a user-level background service when you want the agent to keep watching a folder after you close the terminal. Because marker-pdf can be GPU-heavy, the agent is designed to run as one worker per user and process one document at a time.

The installer detects the current operating system and writes the native service definition for that platform:

• macOS: user LaunchAgent plist in ~/Library/LaunchAgents/
• Linux: systemd user unit in ~/.config/systemd/user/
• Windows: setup instructions for NSSM or a pywin32 service wrapper in .marker-pdf-agent/windows-service.md

Install a service for a managed folder:

marker-pdf-agent install-service --root /path/to/folder

Then start it with the command printed by the installer. On macOS this is a launchctl bootstrap ... command. On Linux this is a systemctl --user daemon-reload && systemctl --user enable --now ... command. Windows needs an additional service host, because Python cannot install a native Windows service without one.

Check or remove the service definition:

marker-pdf-agent status
marker-pdf-agent uninstall-service

The --service-name option changes the installed service definition name. It is mainly useful when replacing or testing service definitions. Running multiple agent services at once is not recommended.

marker-pdf-agent install-service \
  --service-name marker-pdf-agent \
  --root /path/to/folder

Service logs are written under the managed folder in .marker-pdf-agent/service.log and .marker-pdf-agent/service.err.log.

Development

Development, test, quality-check, and publishing notes are in DEVELOPMENT.md.

License

This project is released under the MIT License. See LICENSE.

The tray icon is derived from the MIT-licensed file-markdown SVG from SVG Repo: https://www.svgrepo.com/svg/332064/file-markdown.