/projects
A project is the namespace an initiative runs in: its team, the agents feeding it, and the sources it references. The project switcher at the top of the sidebar scopes the Inbox, feeds, Agents, and Reports to the active project’s repos and experiments.
The Projects index lists each project with its team, agent count, and source count. + New project creates one inline; open a project to edit it.
Scope
Free text, edited any time — e.g. “Focus on the retrieval and prompting pipeline; ignore CI/infra changes.” Recommendations, agents, and gates all read this: saving it refreshes the project’s interests, so it’s the cheapest way to steer what the whole loop pays attention to.Agents
The agents linked to this project, as chips — add from your installed agents, remove with a click. An agent can belong to several projects.Sources
The connected accounts this project references, grouped by role:
Linking references a connected account for this project; the account itself is connected once under Connectors.
Experiments
The project’s experiment history, extracted from its repos’ merge logs — each row a change with its status, decision, and date. Refresh extraction re-reads the merge log; individual rows can be excluded (and restored) to curate what feeds ranking. Agent drafts file here as proposed experiments; merged work and extracted history join them. This history is what agents rank candidates against — it’s the “what your team has actually shipped” signal.The Pro quality gate
Three sections put a quality gate between agent drafts and your main branch. They carry a Pro badge — Remyx sets them up with you (self-service is coming; contact us):1
Target metrics
What “better” means for this project: each metric with a baseline and a target. Metrics frame what agents recommend and what validation gates against.
2
Evaluation
Locked eval templates: the scoring harness is committed before results exist, so nobody moves the bar after seeing them. Future experiments inherit the most recently locked template.
3
Decision policy
Three cards — Ship, Reject, Iterate — rendering the promote bar at the gate. Ship and Reject are rules over your metrics (≥, improves-by, no-regression, …); Iterate is the automatic fallback when neither matches. Evidence is posted right on the PR.
Danger zone
Delete this project removes its configuration and unlinks its experiments. It cannot be undone.Related
Evaluation & decision policy
The Pro gate in detail
Agents
The agents a project links
Connectors
Connect the accounts projects reference
Reports
Fleet output, scoped by project