OpenReflex
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENREFLEX_HOME | No | Set to relocate the data directory (default is ~/.openreflex). | |
| OPENREFLEX_DISABLE | No | Set to 1 to turn capture off everywhere. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_execution_contextA | Retrieve relevant past experience for a task, with 2-3 scored candidate strategies, likely files, and lessons. Call before substantial work when no [OpenReflex] context was injected. |
| choose_pathA | Declare the strategy you are following (a suggested one like 'test-first', or your own with steps). Improves regret analysis, which otherwise infers the path from tool activity. |
| record_outcomeA | Record the verified outcome of the current task, e.g. status='success', evidence='pytest -q passed'. |
| search_experienceB | Search past task experiences in this project by description similarity. |
| explain_nodeB | Show an Experience Graph node and its direct relations (used, caused, failed_with, resolved_by, recommended_for). Embeddings are omitted. |
| project_insightsC | Capture health, experience reuse, efficiency, Execution Regret trend and routing agreement. |
| approve_projectA | Enable OpenReflex capture for this project. Only call when the user explicitly asked to enable it. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool serves a distinct function: context retrieval, strategy declaration, outcome recording, experience search, graph exploration, insights, and project approval. There is no overlap in purpose.
Most tools follow a consistent verb_noun pattern (get_, choose_, record_, search_, explain_, approve_), but 'project_insights' breaks the pattern by being noun-first. Overall readable and predictable.
Seven tools is well-scoped for an experience management server, covering retrieval, capture, strategy, insights, and activation without being sparse or bloated.
The tool surface covers the core lifecycle (retrieve, capture, declare, search, inspect, analyze) but lacks explicit editing or deletion of experiences, a minor gap for full CRUD coverage.