> For the complete documentation index, see [llms.txt](https://docs.sola.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sola.security/getting-started/release-notes.md).

# What’s New

**July 12, 2026**

Here’s the latest on what’s new and improved at Sola.

## *New* Agents and Skills

Investigate alerts, triage incidents, and take action across your connected environment with [**agents**](/workspace/agents.md) you @mention from any chat or project. Agents work asynchronously while you stay in the conversation. Start with a pre-built agent from Sola or build your own, each with its own instructions, tools, and memory.

Apply domain-specific expertise to any investigation with [**skills**](/workspace/skills.md) you invoke with / in chat, or assign to agents to extend what they know without rewriting their instructions. Start with pre-built skills from Sola or build your own.

<div><figure><img src="/files/fMNBujNnnBuJjkuY6avq" alt="Custom agents, ready when you need them"><figcaption><p>Custom agents, ready when you need them</p></figcaption></figure> <figure><img src="/files/Ay7qNfZy4EUoQsa9Kwef" alt="Reusable skills your whole workspace can use"><figcaption><p>Reusable skills your whole workspace can use</p></figcaption></figure></div>

***Available on*** [***paid plans***](https://sola.security/pricing/)***.***

{% embed url="<https://sola.security/pricing/>" %}

## *New* in Lumina Signals: investigate your risks in chat and view them in a focused feed

A new [**feed view**](/workspace/lumina-signals.md#feed) shows your most important risks grouped by security domain, led by a personalized brief that highlights the day's top priorities.

Start a [**chat**](/workspace/lumina-signals.md#investigating-signals-in-chat) from any signal to investigate it with full context, ask follow-up questions, and dig into several signals at once. Your investigation stays in your workspace to reference and build on, even after the signal resolves.

<div><figure><img src="/files/nT4Fu3ZloYchiZXON2RP" alt="Lumina Signals"><figcaption><p>Your most critical risks, pre-investigated and prioritized across your entire environment</p></figcaption></figure> <figure><img src="/files/2kGrqQRbXRzTOwLKEaSD" alt="Investigate any signal in a chat"><figcaption><p>Investigate any signal in a chat</p></figcaption></figure></div>

## Integrations

<figure><img src="/files/g7x1w4NtfmdyQVzs3YcJ" alt=""><figcaption></figcaption></figure>

### Data Sources

***New***: Claude Enterprise Analytics

[Monitor how Claude](/integrations/data-sources/claude-enterprise-analytics.md) is adopted and used across your organization. Track per-user activity, active users and seats, skill, connector, and project adoption, and token and cost usage.

[**Try these updates now**](https://auth.sola.security/oauth/account/login)

<a href="/pages/tdAsgMxEjtk7c059Lt7i" class="button secondary" data-icon="megaphone">Read the full product updates changelog</a>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sola.security/getting-started/release-notes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
