Overview
Logical is designed to understand what you’re working on, allowing it to provide highly relevant assistance without you needing to manually provide context. By analyzing your active applications, windows, and attached Knowledge Bases, Logical can offer proactive suggestions and execute complex commands accurately. This context is gathered in two primary ways: Named Tasks and Sticky Tasks.How Logical Gathers Context
Named Tasks
A Task is a collection of application windows that you group together for a specific job. This is the most powerful way to provide Logical with context, especially for work that spans multiple applications. When you ask a question or issue a command while a Task is active, Logical uses the content from all windows within that Task, as well as any attached Knowledge Bases, to understand your request and perform the right action.For a detailed guide on creating and managing Tasks, please see our Tasks documentation.
Sticky Tasks
A Sticky Task is a more implicit way of providing context. When this feature is enabled, Logical treats your currently active window as a temporary, single-window Task. This is useful for quick, in-the-moment questions related to what you’re looking at, without the need to formally create a Task. For example, if you have a code file open and ask, “What does this function do?”, Logical will use the content of that file as context.“Sticky Tasks” is an optional feature that can be enabled or disabled in the Privacy Settings.
What’s Included in the Context?
When you interact with Logical, it considers the following sources to build a complete picture of your work:- Application Windows: The content of all windows included in your active Task (either named or Sticky). This may include visible and non-visible content.
- Knowledge Bases: Any Knowledge Base you have attached to the current Task.