Everyday examples

These are prompts you can give a connected coding agent. Replace acme/service and the example paths with your own repository and files. Check that your agent actually calls Lore instead of answering from its existing conversation.

Start work on an unfamiliar area

Before changing src/payments in acme/service, use Lore to load the relevant conventions and gotchas. Explain which ones affect the change I requested.

The agent should call get_context with that repository and path. Review the returned claims before editing. If there are no facts, inspect the code normally; empty memory is not permission to guess how the system works.

Understand an earlier decision

Search Lore in acme/service for why payment retries reuse the original request ID. Show the evidence for any explanation you find.

The agent should use search. A useful answer identifies the decision and links to its evidence. If no evidence supports the proposed explanation, ask the agent to say so rather than present an inference as an established decision.

Record something the team learned

We confirmed that payment retries must reuse the original request ID to avoid duplicate charges. Record this as a gotcha in acme/service, scoped to src/payments, with the tag retries.

The agent should call record and return the saved fact. You need write access. Keep the note specific enough that another person can act on it later.

Compare these claims:

• Too vague: “Be careful with retries.”
• Useful: “Reuse the original request ID when retrying a payment, so the provider can detect duplicate requests.”

Retire a rule that no longer applies

Find the Lore fact about manually refreshing sessions in acme/service. Show me the fact and its evidence first. After I confirm, retire it because the new client now refreshes sessions automatically.

The agent should search first and use forget only for the fact you identified. Retiring it changes shared memory for other users too. It does not delete the underlying GitHub comment or source file.

Compare memory with the code

Load Lore's context for src/auth in acme/service, then compare its claims with the current code. Flag disagreements for review; do not automatically rewrite code to match an old fact.

Lore supplies context and evidence. Your agent still needs to inspect current code and run the checks appropriate to your project. Memory can become outdated.

Work across several repositories

List the repositories available through Lore. Then search only acme/api for API versioning decisions, and only acme/web for how the client handles old versions.

Use explicit repository names to keep results understandable and avoid ambiguity when you belong to several organizations.