/research?mode=feed
Track research interests and review recommendations associated with your repositories. Each recommendation is a candidate to inspect, not a guarantee that a change should be implemented.
Research Interests
Research Interests are the context that drives your recommendations. Each interest has its own name, context description, and recommendation cadence.Creating an Interest
Click + New Interest at the top of the Feed view.
You can seed an interest from free text, from a GitHub repo (see below), or from an existing Project. The Project source draws on that project’s experiments, so the ranker scores candidates against the work you’ve actually run.
Interest Pill Tabs
Your interests appear as pill tabs at the top of the Feed:- All — Combined feed from all interests
- [Interest Name] — Filtered to that interest only, with badge count showing how many new recommendations are available
Managing Interests
Click the gear icon (⚙️) next to an interest name to:- Edit the name, context, or daily count
- Toggle active/inactive (inactive interests stop generating recommendations but preserve history)
- Delete the interest
Research Interests from a repo
Instead of a free-text context, you can create an interest from a GitHub repo (pick one from your connected GitHub, or paste a public URL). Remyx extracts the repo’s merge history into a structured shipping record in the background, then ranks recommendations against the work your team has actually shipped. This is the same extracted history that powers a Project; a repo-driven interest and a project that links the same repo converge on one history. Profiling reads the whole tree, not a truncated path list: a directory-level inventory of what the repo covers (largest groups first), the high-signal files, and a commit timeline sampled across the repo’s history rather than only its head. The report it produces is editable and becomes the interest’s context. A repo-backed interest also triggers a typed, cited deep-research brief for the repo. Its “future directions” become a forward-looking ranking axis alongside your shipping history, and its “candidate changes” seed recommendations, so the feed can weigh where the work is headed. When you create an interest from a repo, the dialog also offers an auto-PR setting that can provision automated discovery PRs for that repo:Recommendation Cards
Each recommendation shows:
Cards are sorted by recency by default. Use the Sort control to change ordering.
Refreshing Recommendations
Each interest has a Refresh button in the toolbar. Click it to trigger an immediate re-ranking — don’t wait until the next scheduled run. Refresh runs asynchronously. A progress indicator shows the status. Navigate away and come back; the job continues in the background.Scheduled recommendations refresh daily at 9:30 AM UTC for all active interests. Use Refresh for instant updates, or update your context sources before the daily run.
How recommendations are ranked
For interests backed by a shipping history (any repo-sourced interest or a project), ranking goes beyond matching your context text:- Your team’s extracted shipping history is fed into the ranker, so candidates that align with the methodological direction you’ve actually shipped rank above ones that are merely topically related.
- A learned preference model, fit over your past experiments, scores candidates and breaks ties behind relevance.
- A Semantic Scholar candidate source: the Semantic Scholar Recommendations API is seeded from your merge history (shipped work as positive examples, rejected work as negative, plus the brief’s candidate changes) and its results are merged with the nearest-neighbour and recency candidates before ranking. Items from this source carry a “Powered by Semantic Scholar” attribution.
Resource Detail & Chat
Click View on any recommendation to open the detail page with:- Details tab — Full abstract, resource links, citations, Docker availability
- Chat tab — Ask questions about the resource in natural language with streaming responses
From Feed to agent
The feed is the same candidate stream your agents draw from: a repo-backed interest is the input to an agent, and the auto-PR setting above is how a feed becomes a running agent. Once installed, the agent ranks this stream against your shipping history, drafts the best fit, and your merges and skips sharpen what the feed surfaces next.CLI & API
You can also access your feed programmatically. By default the digest honors each interest’s per-day limit; the API’s unlimited mode (limit=0) returns every alerted recommendation instead, along with a truncated flag indicating whether anything was held back.
Related
Agents
Turn a repo-backed interest into a running agent
Search
On-demand semantic search across all resources
CLI: Interests & Papers
Manage interests and recommendations from the terminal