Repository / project instructions
Compare the documented files, rules, and project contexts that keep durable guidance with the work.
Ask Product Fit
Find evidence-backed AI product fit for your workflow
Choose workflow requirements and inspect which products are supported by reviewed evidence, where evidence is incomplete, and where a requirement falls outside covered scope.
Selections stay in this browser and are not sent to a server. Every result links back to the reviewed evidence behind it.
Product Fit controls
Describe the workflow you need to support
Select one or more requirements. A surface filter is optional and keeps each conclusion within the scope established by the reviewed evidence.
Product Fit results
Evidence for the selected workflow
These groups describe the selected evidence and scope. They are not rankings or universal product verdicts.
Evidence-backed fit
Evidence insufficient
Outside covered scope
Workflow requirements
Start with the work that needs support
Ask Product Fit uses the same reviewed question set as Behavior Intelligence. These are workflow questions, not an independent capability list.
-
01 -
02 Persistent / custom instructions
Compare user, project, workspace, and managed instruction layers that can carry guidance beyond one immediate request.
-
03 Memory / persistent context
Distinguish documented memory systems from authored instructions and from context that exists only inside a current task.
-
04 Planning / work decomposition
Compare evidence for plan creation, plan updates, or planning tools without assuming one universal agent workflow.
-
05 Tools / tool calling
Compare the selected evidence for agent tools while retaining product, model, plan, and configuration limits.
-
06 Filesystem / file modification
Compare source-backed file and workspace operations without equating uploaded-file analysis with filesystem modification.
-
07 Shell / terminal execution
Compare documented command-execution capabilities and the harness controls that may constrain them.
-
08 Browsing / network access
Compare explicit web, search, research, and external-resource evidence without treating all tools as network access.
-
09 Approvals / permissions
Compare user approvals, allow/deny rules, confirmation, and isolation controls that sit around tool execution.
-
10 Context scope / inheritance
Compare how product, surface, model, repository, project, workspace, user, and configuration boundaries shape documented context.
Evidence states
Read the evidence before drawing a conclusion
Not established means selected evidence does not establish the claim. It does not show that the capability is absent.
- Documented
- The selected first-party sources or product evidence directly establish the behavior.
- Observed
- Reviewed observations establish the behavior. This matrix adds no new observed claims.
- Not established
- The selected evidence does not establish the answer. It does not show that the capability is absent.
- Out of scope
- The question does not apply to the covered product or surface; the answer explains why.
Product Fit
Three ways a workflow can be represented
The result groups describe the evidence for selected requirements. They do not provide a universal product verdict.
Evidence-backed fit
Every selected workflow requirement is documented or observed within the applicable scope.
Evidence insufficient
At least one required claim is not established, or the available evidence does not establish the requested scope.
Outside covered scope
A requirement falls outside the covered scope or conflicts with the requested surface.
Scope matters
Keep each conclusion in its documented context
Evidence can apply to a product, surface, model, or configuration. A behavior documented for a CLI does not automatically apply to an editor or web surface.
When the selected evidence does not establish a surface, model, or configuration, that scope remains unknown rather than being broadened from the product name.
Method and evidence
Trace each decision back to reviewed material
Ask Product Fit derives its evidence from reviewed Behavior Intelligence, registered product evidence, and existing curated comparisons where they provide relevant context.
Coverage is limited to selected, reviewed evidence. It does not claim exhaustive product coverage or live vendor monitoring.
Registered products
Explore the six products represented by current evidence
Products appear in alphabetical order. Their placement here does not imply a recommendation.
Current scope
Product behavior evidence only
Ask Product Fit addresses product behavior in a workflow. Prompt recommendations and prompt compatibility are not part of the current scope.