Compare sources and make a recommendation

Scope: Work with local source material in the desktop app.

Give Remy the material you want to compare and a clear question. Use it to identify differences, check the evidence, and make a recommendation with explicit conditions. This example uses text you provide and does not require a connection to another app.

1. Prepare the material and question

Paste short sources directly into a message. For local material, place text or Markdown files in a folder already added to your Remy project and specify their relative paths in the task.

Explain the decision you need to make, such as “Which process should we use to handle user feedback?” Include the requirements it must meet. Asking only for a summary will not necessarily answer that decision.

2. Try a complete example

The following material is fictional and provided for practice. Send the whole prompt, or replace the sources with your own.

We need to choose a user-feedback process for a five-person product team.
Compare the following material only. Do not browse for additional information or assume capabilities that are not described.

[Team requirements]
Every feedback item must have an owner and a status, and its original description must remain accessible.
The team wants to reduce manual organization, but has not measured how much time that takes each week.

[Option A description]
Users send feedback by email. Operations copies it into a shared spreadsheet with a link to the original email, an owner, and a status.
Owners and statuses are maintained manually. In the past two weeks, the team received 40 feedback items and found three duplicate records.
Costs and long-term maintenance time are not provided.

[Option B description]
Submitting a form creates a ticket that records the original description, an owner, and a status. Tickets can be filtered by status.
The provider has not stated whether duplicate feedback can be merged, and has not supplied costs or measured time savings.
The team has not tried it yet.

Provide:
1. A comparison against each required condition, with the source for each claim.
2. A clear distinction between stated facts, reasonable inferences, and missing information.
3. One conditional recommendation and what we still need to verify.

Do not turn “creates a ticket” into “automatically removes duplicates.” Do not invent time or cost savings.

3. Check whether the conclusions are supported

Use these checks for the example:

• Both options record an owner, a status, and the original feedback. These are not capabilities unique to Option B.
• Duplicate records were observed with Option A. The material does not establish whether Option B would solve that problem.
• Option B creates tickets automatically. That does not prove lower total maintenance time.
• No costs were provided, so the options cannot be ranked by cost.
• A recommendation should state its conditions and next checks. An option that has not been tried must not be described as proven.

Apply the same approach to your own material: trace important conclusions back to their sources. When sources disagree, ask Remy to preserve the disagreement and identify the sources rather than silently choosing one account.

4. Add evidence and update the conclusion

When you have a trial record or a confirmed answer, continue in the same chat:

Here is an additional trial record.
Update the comparison and recommendation. Explain which conclusions change and which still lack evidence.
Keep the original and new sources distinct. Do not extend the trial results to scenarios that were not tested.

[Paste the new trial record here]

5. Save a result you can use

After checking the conclusions, ask Remy to write them to a Markdown file in the project:

Turn the checked conclusions into a one-page decision memo at docs/feedback-workflow-comparison.md.
Include the comparison, recommendation, supporting sources, and remaining questions.
If the file already exists, explain that first and wait for me to decide whether to replace it.

Change the path to the location you want, then open the file and check its contents.

6. Keep exploring

• Desktop Guide: Add a source folder and view files.
• Model selection and automatic routing: Choose how Remy should select a model before starting a task.
• Turn meeting notes into actions: Organize a discussion into decisions and next steps.