> ## 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.
# Create your project
> Connect a repo and watch Remyx extract structured experiment history from your merge log.
*Setup phase · \~3 minutes*
A **project** in Remyx is a workspace that scopes a set of related experiments. It carries shared context (the eval template, the decision policy, the discovery feed, integration credentials) so individual experiments don't have to re-establish it.
The fastest way to get a project off the ground is to connect a repo and let Remyx extract structured experiment records from the merge history. That's what this tutorial does.
The whole series uses [remyxai/VQASynth](https://github.com/remyxai/VQASynth) as a stand-in example. Substitute your own repo URL anywhere it appears. The flow is identical.
## Connect the repo
1. Open the project switcher at the top of the sidebar and click **+ New project**. (You can also reach the same wizard from the **Projects** page under Manage.)
2. The wizard opens with a tabbed repo picker. Pick your repo from the **From GitHub** tab if it's connected, or use **Paste URL** to provide a public URL. To follow along, paste `https://github.com/remyxai/VQASynth`.
3. Give the project a name (defaults to the repo name) and write a one-paragraph **scope context** describing what you care about. The scope context shapes both the cold-start extraction and downstream recommendations.
For VQASynth, scope context might read:
> Synthetic data pipeline for training spatial-reasoning VLMs. We care about pipeline-stage swaps (depth estimator, segmentation, captioner) and their downstream effect on benchmark accuracy. Not focused on hyperparameter sweeps.
For an LLM application:
> Customer support chatbot built on Claude. We care about retrieval quality, especially for ambiguous tickets, and routing rules that decide when to escalate to a human agent.
For a retrieval system:
> Hybrid retrieval over technical documentation. Prioritizing recall for multi-hop queries and reducing latency on the rerank step.
4. Check **Create a research interest from this project**. The next tutorial covers the digest in detail; checking this here saves a step.
5. Click **Create**.
A background extraction job kicks off as soon as the project is created. It walks the recent merged PRs in your repo and turns each meaningful one into a structured **experiment** (a single tracked change with a hypothesis, a target metric when one is implied, and a link back to the PR).
## Watch the history extract
The Experiments tab fills in as the extraction runs. Records carry a **Backfilled** badge, meaning Remyx auto-extracted them from a merged PR (as opposed to experiments you create manually later).
This extracted history becomes part of your project's standing context. Every experiment you create from here can reference it. Recommendations and decisions get sharper as the context grows.
## See the timeline
Click the **Outcomes** tab. Every experiment under the currently selected project lives here, grouped by date. The chart-mode selector lets you flip between three views (Trend, Velocity, Impact).
The project switcher at the top of the sidebar scopes Outcomes, Insights, and any other project-level view. Switching projects updates all of them at once.
Backfilled experiments often don't have measured deltas. Remyx has the merge but not the metrics, so they appear under a **Baseline only** badge and contribute to velocity but not impact. As you fill in deltas on individual records, the Impact chart populates.
## Recap
You now have:
* A Remyx project linked to your repo
* An experiment record extracted from your repo's merge history
* An Outcomes timeline showing what's shipped under this project
The extraction is the seed of the project's shared context. Subsequent tutorials build on it.
## Next
Turn the extracted history into a daily digest of relevant new work.
See the full arc
Wire up GitHub, Linear, Slack, and Jira
A background extraction job kicks off as soon as the project is created. It walks the recent merged PRs in your repo and turns each meaningful one into a structured **experiment** (a single tracked change with a hypothesis, a target metric when one is implied, and a link back to the PR).
## Watch the history extract
The Experiments tab fills in as the extraction runs. Records carry a **Backfilled** badge, meaning Remyx auto-extracted them from a merged PR (as opposed to experiments you create manually later).
This extracted history becomes part of your project's standing context. Every experiment you create from here can reference it. Recommendations and decisions get sharper as the context grows.
## See the timeline
Click the **Outcomes** tab. Every experiment under the currently selected project lives here, grouped by date. The chart-mode selector lets you flip between three views (Trend, Velocity, Impact).
The project switcher at the top of the sidebar scopes Outcomes, Insights, and any other project-level view. Switching projects updates all of them at once.
Backfilled experiments often don't have measured deltas. Remyx has the merge but not the metrics, so they appear under a **Baseline only** badge and contribute to velocity but not impact. As you fill in deltas on individual records, the Impact chart populates.
## Recap
You now have:
* A Remyx project linked to your repo
* An experiment record extracted from your repo's merge history
* An Outcomes timeline showing what's shipped under this project
The extraction is the seed of the project's shared context. Subsequent tutorials build on it.
## Next