LogicLens
Understand rules inside the code.
Explore code as a network of steps, rules and connections.
Understand rules inside the code.
When understanding a function, investigating design choices or choosing where to intervene.
Small implementation choices can have large effects: defaults, conditions, retries and error handling may not be mentioned in a short chat answer. LogicLens exposes supported code structure and recorded activity.
Explore the graph, open a node, inspect its source and describe a requested change in ordinary language. Keep source analysis separate from measured execution.
Take a closer look.
Explore the actual screens and controls. Click an image to see every detail.
How to get started.
From your first choice to the result. Here is how to use this feature in your own project.
- 01
Open the separate grid window. Pan, zoom and choose plain-language explanations or source code.
- 02
Select a tile for its source location, known values, relationships and details. Run analysis to examine current files again.
- 03
Describe a change for a step and send it to the conversation, queue or active task.
How it could work for you.
Inspect whether a failed data source stops a whole process or is skipped, then request the intended behaviour.
How to assess the result
A parser cannot prove every runtime path. Hidden model reasoning and unreported internal operations are not available.
Where to find it.
Conversation → Tools → LogicLens
Available actions depend on your plan, mode and project state. Features that require a task become available within an appropriate conversation.What is saved?
Available source analyses and observed activity stay linked to the project and conversation. Time and model information appears where recorded.
What you need to know
Source analysis describes code; it does not prove the code ran. LogicLens cannot expose hidden thoughts or observe every internal provider step.