Context & usage

Context Inspector

Understand what information is included.

Inspect and manage information you deliberately provide to a task.

01
Inspect the context available for the next request.Actual Linqbase interface · demonstration project
TURN IDEAS INTO POSSIBILITIES

Understand what information is included.

Before a new task or when changing standing project instructions.

A model may need previous decisions but not every old tool result. Context inspection helps you review available sources and the information prepared for a request.

Inspect categories, summaries and remembered project information. Use the existing controls to manage relevant context.

YOUR NEXT STEP

How to get started.

From your first choice to the result. Here is how to use this feature in your own project.

  1. 01

    Review the goal and available context information.

  2. 02

    Add standing instructions and exclude files from the selected context.

  3. 03

    Check preparation of the next request before continuing.

IN PRACTICE

How it could work for you.

Keep the approved design decisions while checking whether a large outdated log still needs to be included.

How to assess the result

A summary can omit detail. Retain source evidence for decisions that must remain exact.

GET STARTED IN LINQBASE

Where to find it.

Composer → Context circle → Context; also available in Tools

Available actions depend on your plan, mode and project state. Features that require a task become available within an appropriate conversation.
SAVE & CONTINUE

What is saved?

Standing instructions are saved for the project and used where the selected route supports them.

GOOD TO KNOW

What you need to know

This does not expose hidden thoughts or every internal model context. Excluding context is not general file protection against all terminal commands.