Effective workflows
Find the workflows that keep shipping. Storybook first for frontend work, Skill X for migrations, MCP Y for low-churn changes.
Learn from every session your team runs.
Capture what works across AI coding sessions and turn it into shared team knowledge.
Capture the work around the code.
Code is no longer the only output. Reflex observes the session mechanics that explain why a run succeeded, failed, got steered, or became expensive.
Prompts and steers
Tool and MCP usage
Skills, rules, and agents.md files
Retries and model switches
Code churn and review outcomes
Cost and time to completion
Go incognito when the work needs privacy.
Disable capture for sensitive sessions without changing the rest of your team setup. Reflex is built for shared learning, not surveillance.
Turn repeated behavior into team standards.
Reflex looks for patterns that can become skills, agents.md guidance, model defaults, harnesses, and review checklists.
Waste and drift
See where agents burn tokens, repeat dead ends, ignore existing patterns, or keep using skills that are not helping.
Codebase footguns
Surface the places where agents and engineers repeatedly miss permissions, validation, schemas, or release steps.
agentrelay-learning/
- skills/frontend-forms.skill.mdWorkflow copied from shipped form changes
- agents.mdRepository defaults for planning and review
- rules/auth-permissions.mdGuardrail from repeated policy misses
- mcp/playwright-harness.mdBest-value browser check for UI work
promoted from sessions
Session pattern accepted by reviewers
Tool sequence reused with low churn
Private run excluded from team memory
Every session becomes better context for the next one.
Reflex builds on Agent Relay's event stream, search, and team messaging layer. The result is a living memory of how your agents actually get work done.
Ask how your team usually solves the problem.
Plans should come from learned truths in your own repository, not generic internet advice or a teammate's memory.
reflex.memoryteam history
$How do we usually build React forms?
>Searching the last 14 shipped React forms
Engineers typically:
- Start from FormTemplate.tsx
- Install the team form skill
- Use the validation MCP server
- Check the schema issue that caused three reverted PRs
Pair with the history of your team.
Real-time guidance calls out common failure modes while an engineer or agent is still in the session.
Engineers usually forget to update permissions when modifying this service.
This approach caused five reverted PRs.
The last three similar changes used a different workflow.
Make your team better with the sessions you already pay for.
Reflex helps engineering leaders see whether agent usage is compounding into standards, savings, and faster onboarding.
Are we getting better?
Where is money being wasted?
What workflows should be standardized?
Who discovered something useful?
What knowledge is trapped in individuals?