Setup phase · ~3 minutes A generic AI discovery feed surfaces what’s hot. A discovery feed grounded in your project surfaces what’s relevant to the directions your team has actually shipped, ranked against real history. In this tutorial, you’ll wire up that feed using the experiment history from the previous tutorial so the recommendations Remyx delivers are scoped to your work.Documentation Index
Fetch the complete documentation index at: https://docs.remyx.ai/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites. You’ve completed Create your project. The project has finished cold-start extraction.
What a discovery feed gives you
A research interest is a saved configuration that tells Remyx what kinds of papers, repos, models, and datasets you want to hear about. The system runs daily and surfaces the top results that match, ranked against the experiments your project has already shipped. In practice, this means:- A paper about a new depth estimator gets ranked higher if your project has been swapping depth estimators.
- A retrieval rerank technique gets ranked higher if your project’s history shows retrieval-quality experiments.
- Off-direction work (an unrelated benchmark, a refactor framework) gets pushed down or filtered out.
Create the interest from your project
If you checked Create a research interest from this project during the wizard in the previous tutorial, an interest already exists for this project. Skip to the curation step below. Otherwise:- Open Feed in the sidebar and click + New Interest in the page header.
- Pick the From project tab (it’s the default).
- Select the project you created in the previous tutorial.
- Save.
Curate the experiment list
The pre-filled list is a checklist. The experiments you keep checked are the signal Remyx uses to rank papers. The experiments you uncheck become noise to ignore. Keep:- Model swaps and architecture changes
- Evaluation method changes (new benchmarks, new metrics)
- Routing or policy changes
- Prompt-engineering experiments
- Data-pipeline-stage upgrades
- Pure refactors (file moves, type-hint cleanups)
- Dependency bumps
- Security patches
- Infrastructure-only changes (CI, build, packaging)

Set the daily count
In the interest’s settings, choose how many recommendations you want delivered each day. You can update this value as needed.Recap
You now have:- A research interest that knows your project’s direction
- A daily count for how much research Remyx surfaces
- A feedback loop where curating the experiment list sharpens future recommendations
Next
Define how progress gets measured
Lock in the eval template and decision policy that future variants will be judged against.
Wire your feed into Slack
Daily digest delivery in Slack
Series overview
Full series arc