Research Library

The Research Library is the analyst’s workspace: a tree of Markdown documents organized by category, a built-in editor, and the source materials behind every report. Research results, plans, and cycle documents all land here.

Document tree

Documents are organized into a tree of categories with navigation. Every file carries a frontmatter header with title, order, and description: the tree builds its labels and ordering from these. The tree is re-read whenever something changes, so new reports and edits appear instantly — updates happen on the fly, with no reload.

New and updated documents are highlighted in bold in the tree — the document itself and every folder above it; open a document and the highlight is gone. An update is decided by the document’s content, not by its date, size or owner: a copy or a permission change does not raise the highlight, while rewritten text does. The highlight survives a restart.

History, search, and filters

In a large library, documents stay easy to find. Next to the search box in the sidebar sits a clock button: it switches what the list shows — the full tree, recently viewed, recently updated, or recently created documents. “Recently Viewed” is stored on this device, while “Updated” and “Created” are derived from the files’ timestamps.

Search is full-text: as you type, it looks through titles, paths, and document bodies. You can also filter the library by document properties (frontmatter) — for example, keep only the documents tagged with a certain tag. You compose such queries in the advanced search dialog, and the available field values are suggested for you automatically.

Any document can be given an icon from the built-in collection — the category tree becomes easier to read, and the section you need is found at first glance. The first row of the tree, the home page, carries the same actions as any document: the three-dot button and the right-click menu offer Update Icon and Mark As Read. Mark As Read on the home row marks every document as read at once and clears the highlight across the whole tree; Update Icon writes the home page’s own icon into its file and replaces the default house icon with it — clear it and the house comes back. Each page remembers its scroll position for a day: open a document, and you are exactly where you left off. At the bottom of the sidebar are the “Prompts (N)” and “Chats” buttons: the first opens the shared prompts queue (see “Prompt Queue“), the second the list of agent chats.

Pictures and files in documents

A document can show pictures right in its text and hand attached files over for download. An image (png, jpg, jpeg, gif, webp, avif or svg) is inserted with ordinary Markdown markup and appears in the reader; any other file — a PDF, a presentation, an archive — becomes a link that downloads on click. The attachment sits next to the document, in its own folder, and the link points at it relative to that folder (an absolute path under /docs/… works too): the report stays whole, and its diagrams and appendices travel with it. On disk the link stays clean and relative, while the address the app serves is signed and short-lived.

Attachments never appear in the document tree: the portal lists the Markdown documents themselves, so a file is reachable only from the report that links to it. Everything else is left exactly as written — external https:// links, # anchors, links to other .md documents and text inside code blocks. A missing file is not fixed silently either: a typo shows up at once as a broken picture or a dead link.

Editor

The built-in editor with syntax highlighting (CodeMirror) lets you edit any document right in the browser — reports, plans, cycles. It is plain Markdown: files can be edited, deleted, and extended without restrictions.

Report sources

Every report shows its history: the search sessions and the downloaded pages it was assembled from. The downloaded Markdown is read right in the interface — you can check any fact against the original in one click, without leaving the app.

Edit with AI and “Call Agent”

Next to the edit button sits an AI icon. It opens a panel with a prompt field: describe what to change in the document, and the prompt goes to Agent (a request to {AGENT_API_URL}/api/remote/chats), which performs the edit. The absolute path of the research is substituted into the prompt automatically, and the model is picked from the model list the Research reads from the agent itself — each model shown with its color label. The finished agent chat opens from the interface.

The feature is enabled by the AGENT_API_URL and AGENT_API_KEY variables (set together); without them the buttons are hidden. Learn more in Agent Integration.

Agent chats

The “Chats” panel complements the library: Agent chats with real-time updates — the agent works on the documents while you see every step in the same window.

← Back to documentation