Context

​

Why context is its own layer

An agent that can’t see your environment is guessing. Console’s agents don’t answer from a static index or a model’s memory of open-source code — they read your actual files, run commands against your actual repository, and query the findings your existing tools have already produced. That means the quality of everything downstream depends on what you’ve connected.

​

Two kinds of context

Projects are what an agent reads from disk. Connections are what it queries over the network — including the pull request events that let a workflow fire on its own.

​

Two ways to direct it

Having context isn’t the same as using it. Console gives you an interactive path and a declarative one:

• Chat — point an agent at something and ask. Best when you don’t yet know what you’re looking for, or when the question is a one-off.
• Workflows — declare the repositories, the agent chain, and where results go, then let it run unattended. Best when the task is worth repeating.

The usual progression is to explore a question in chat, and once the approach works, promote it to a workflow.

​

What accumulates

As agents work, results collect in your organization rather than evaporating with the conversation:

• Findings — confirmed issues, each with the agent’s reasoning, the affected code, and often a suggested fix.
• Detections — the rules you’ve built up, which later runs apply automatically.

Both become context in their own right. A finding can seed a new chat; detections turn a one-time discovery into a permanent check.

​

Next steps