# April 26: Support for fact evidence citations, targeted distribution, agent modes

### New Features

* 💡 Graphlit now supports **fact evidence citations** via `FactEvidence` and `FactCitation`, making it easier to trace extracted facts back to supporting content or conversations.
* 💡 We have added **targeted distribution** support with `DistributionTarget`, operation/kind enums, and provider-specific properties for Notion, Google Drive, OneDrive, Confluence, Slack, Gmail, Outlook, HubSpot, Salesforce, Attio, Google Calendar, Microsoft Calendar, Linear, Jira, Zendesk, Intercom, Google Docs, Microsoft Word, SharePoint, Discord, Teams, X, GitHub, GitLab, and LinkedIn.
* We have expanded **Agent APIs** with durable modes, commands, heartbeat settings, research depth, persona/specification references, content filters, and distribution targets.
* We have added **GPT Image-2** and new image publishing controls for quality, width, height, output format, compression, and moderation.
* We have added **LinkedIn distribution and search** configuration for publishing LinkedIn posts and filtering LinkedIn search by date range.
* We have added additional distribution discovery types, including `IssueDistributionDiscoveryResults`, to support more precise issue-targeted publishing workflows.

### Bugs Fixed

* Improved Gmail feed timeout recovery for newly created feeds with large mailboxes.
* Fixed image publishing prompt compilation so generated image requests preserve the intended prompt structure.
* Improved Notion parsing resilience by preserving unknown block, property, file, parent, and rich text object types instead of failing deserialization.


---

# Agent Instructions: 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:

```
GET https://changelog.graphlit.dev/april-2026/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
