> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/changelog/readme.md). # Product updates A full rundown of the latest releases, improvements and fixes in Lleverage {% updates format="full" %} {% update date="2026-10-12" tags="new-releases,improvements,fixes" %} ## Week 42: the Agent builds with you {% embed url="" %} This week the Agent learned to build most of what you would otherwise build in Lleverage yourself. Ask it to set up a project, a dashboard or a workflow, or talk it through on a call. You can also put it to work inside a workflow. It reads your systems before it asks you anything, and it checks with you before anything goes live. ### New features * **The Agent sets up your project.** Start from one of six processes, such as Quote & Sell or Pay & Collect, or start blank. The Agent connects your systems, adds the team, writes its instructions and hands over the first jobs, as a plan you can follow. [Projects and solutions](https://docs.lleverage.ai/understand-lleverage/readme/projects-and-solutions) * **The Agent builds your dashboards.** Ask for what you need to see, such as "orders waiting on a PO and handling time per day", and it adds the widgets to your Overview from your live data. Each role can have its own Overview. [Project overview](https://docs.lleverage.ai/run-operations/overview/project-dashboard) * **The Agent builds and fixes workflows.** Open the Agent beside the canvas and ask for a change. It knows the workflow you have open, highlights the steps it changes, can run the workflow again after a fix, and asks before it puts anything live. [Build a workflow](https://docs.lleverage.ai/build-and-improve/automate/build-a-workflow) * **Talk to the Agent while it builds.** Start a voice call and talk a workflow, a dashboard or a whole project into place. The call follows you to any page in the project. [Call with Agent](https://docs.lleverage.ai/run-operations/agent/call-with-agent) * **Put the Agent to work inside a workflow.** Add the Agent as a step and describe the job in plain words. It can use any Skill or integration you can, and asks a person when something is missing, such as a PO number. [Agent step](https://docs.lleverage.ai/build-and-improve/automate/advanced-workflow-building/agent) * **Work through records on a board.** Show a data table as a board with a lane per status. Drag a card to the next lane and the record's status changes with it. [Tables](https://docs.lleverage.ai/build-and-improve/intelligence/tables) * **Skills that improve from how they're used.** A Skill's **Feedback** tab collects every rating on work where it was used. Choose **Improve with agent** and the Agent drafts a change for you to approve. [Skills](https://docs.lleverage.ai/build-and-improve/intelligence/skills) ### Improvements * **Type while the Agent works.** Send a message mid-task and the Agent takes it into the task it's on. * **Hand the Agent your files.** Up to 50 files per message, Excel files shown as a real spreadsheet, and Google Drive folders connected to Project Files and kept in sync. * **Know what the Agent made.** The Agent sidebar lists everything the Agent created in the session, and the Agent links straight to the pages it means. * **Decide with the full picture.** Zoom into a request's attachments and click through them; in Apps, **Edit and resubmit** corrects a form you already sent. * **Team and access in one place.** Members and Roles tabs with a simpler role editor, seats and invites as one self-serve flow, and with single sign-on, invites only to your company's domains. * **Claude Haiku 5.5 for quick steps.** Choose **Fastest** in any model picker. ### Fixes * The Requests page opens PDFs reliably after you approve a request, and your queue filters stay in place after a refresh. * A shared link to a request opens that request, whatever view you are on. * A voice call stays connected while you sign in to an integration. * Large table imports that replace all rows finish without timing out. {% endupdate %} {% update date="2026-10-02" tags="new-releases,improvements,fixes" %} ## Week 40: Project Files in workflows and reopened requests Workflows can now use the same Project Files as people and the Agent, and a completed request can be reopened when something needs another pass. The Agent can also look up who changed what in your organisation. ### New features * **Project Files in workflows.** Workflow steps can read and write the same Project Files that people and the Agent use, in manual, scheduled and triggered runs. [Files](https://docs.lleverage.ai/build-and-improve/intelligence/files) * **Reopen a completed request.** Eligible assignees can reopen a completed request and run the work again from that handoff. This creates a new request and replaces pending requests in the same session that the new run supersedes. [Requests](https://docs.lleverage.ai/run-operations/request-inbox) * **The Agent can check audit history.** Ask the Agent who changed a setting or resource, and when. It only shows what you have access to. * **GPT-6.1 Sol as an Agent model.** Available in the Agent model list, served through OpenAI's EU endpoint. [AI models](https://docs.lleverage.ai/administer-and-govern/control/ai-models) ### Improvements * **Switching projects.** Opening and switching projects keeps your browser's Back button working. [Finding your way around a Project](https://docs.lleverage.ai/run-operations/overview/navigation) ### Fixes * Customer organisations can set up the Microsoft Teams connection themselves again. [Set up Microsoft Teams](https://docs.lleverage.ai/administer-and-govern/control/channels/set-up-microsoft-teams) {% endupdate %} {% update date="2026-09-25" tags="new-releases,improvements" %} ## Week 39: boards, custom roles and calls with the Agent Data tables can now be worked as boards, projects get custom roles with item-level sharing, and you can talk to the Agent on a live call. ### New features * **Data tables as boards.** Switch any table to a board with lanes by a text, single-select, yes/no or person field. Drag a card to another lane and the record changes with it. [Tables](https://docs.lleverage.ai/build-and-improve/intelligence/tables) * **Custom roles and item-level sharing.** Project Admins can create roles with None, View or Edit access per area, and share single Apps, Workflows, Tables and Knowledge Bases without giving access to the whole project. The Members page shows where each person's access comes from, and admins can preview the project as a member. Existing access is unchanged. [Roles and permissions](https://docs.lleverage.ai/administer-and-govern/control/members/roles-and-permissions) * **Call with Agent.** Start a live voice call with the Agent when talking is easier than typing. The Agent can also suggest a call when it needs you; the call starts when you press **Call**. [Call with Agent](https://docs.lleverage.ai/run-operations/agent/call-with-agent) * **Overviews that build themselves.** An Overview you haven't customised grows with the project: Apps, Workflows, Skills, Tables, open requests and recent items, plus a **How it is going** section once a project has 100 runs in 30 days. Editing turns it into a custom dashboard; **Clear** goes back. [Project overview](https://docs.lleverage.ai/run-operations/overview/project-dashboard) * **Feedback on Agent work.** Rate a single Agent response or a whole session, with an optional comment, and change it later. Builders see the feedback next to the run in Activity. * **Skill Tests for builders.** Builders with the right project access can run tests from a Skill or a Skill proposal. Tests never publish or change the live Skill on their own. [Skills](https://docs.lleverage.ai/build-and-improve/intelligence/skills) ### Improvements * **SharePoint document libraries and large lists.** The Agent can find a site's document libraries and read their files and folders, and large lists are read page by page. Microsoft's limits still apply: a read stops at 5,000 items or 50 pages. [SharePoint](https://docs.lleverage.ai/administer-and-govern/control/connections/sharepoint) * **Replying while an approval is pending.** You can keep typing while the Agent waits for you to confirm a protected change. Your reply adds context; only the confirm button approves the change. * **Built-in industry knowledge.** The Agent can use general industry and process knowledge to ask better questions during setup. Your own rules, policies and master data still come from your project and systems. * **Dashboards in the Lleverage style.** Dashboards the Agent builds use the same look as Lleverage Overview pages, with your organisation's theme. {% endupdate %} {% update date="2026-09-18" tags="new-releases,improvements,fixes" %} ## Week 38: clearer failed runs and a new navigation Failed workflow runs now explain what happened and who can fix it, and the navigation is cleaner and adjustable. ![Widget settings open in the right sidebar](https://3370306531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlgSglJDQZxDZdn20CUcl%2Fuploads%2FHFxsd8y9VnMjEGoKPLlh%2Fwidget-right-sidebar-edit-v2.png?alt=media) ### New features * **Failed runs explained in plain language.** A failed run opens with **What happened** and **What you can do**, in your browser's language where possible, with the raw error underneath. Anonymous Workflow-app viewers still see the raw error. * **Why a run failed, and who acts next.** Failures are classified, for example bad input, a workflow or script error, a provider outage or a timeout, and point to the person who can act next. When the evidence isn't clear, the cause stays **unknown**. Project Admins and Builders get an in-app notification for production failures. [Monitoring](https://docs.lleverage.ai/build-and-improve/monitoring) * **Richer charts on Monitoring dashboards.** Charts built on data tables can be split into series, with your own labels and colours, a date column bucketed by day or week, thresholds and comparisons with the previous period. [Monitoring](https://docs.lleverage.ai/build-and-improve/monitoring) * **Edit widgets in a side panel.** On Overview, Monitoring and Agent pages, switch to edit mode, pick a widget and set it up in the panel on the right. [Project overview](https://docs.lleverage.ai/run-operations/overview/project-dashboard) ### Improvements * **A cleaner, adjustable navigation.** Collapse the sidebar to icons or drag it to the width you want. Pinned pages show recent items on hover, and your organisation's highlight colour runs through the app. Pages stay where they were. [Finding your way around a Project](https://docs.lleverage.ai/run-operations/overview/navigation) * **Messages and tool calls counted apart.** An Agent session's Activity counts messages and tool calls separately, so it matches the transcript. ### Fixes * An Agent step in a workflow that returns no usable text, files or structured result now fails, instead of passing an empty value to the next step. The same goes for missing or malformed JSON output. [Agent step](https://docs.lleverage.ai/build-and-improve/automate/advanced-workflow-building/agent) {% endupdate %} {% update date="2026-09-12" tags="new-releases,improvements,fixes" %} ## Week 37: usage-based billing and Microsoft Teams setup Usage-based billing is live where it is enabled, customers can connect Microsoft Teams themselves, and requests get easier to check against their source PDF. ### New features * **Usage-based billing.** Agent seats are separate from organisation membership. Owners set monthly Agent-usage limits per organisation, project and member, and members can ask for a seat or a higher limit. Reaching a limit pauses new Agent messages, not workflows or scheduled runs. Lleverage turns this on per organisation. [Subscription management](https://docs.lleverage.ai/administer-and-govern/control/settings/subscription-management) * **Set up Microsoft Teams yourself.** Organisation Owners can start the Teams connection in Lleverage and finish it with their Teams administrator. [Set up Microsoft Teams](https://docs.lleverage.ai/administer-and-govern/control/channels/set-up-microsoft-teams) * **Teams channel messages with images and files.** The Teams channel-message trigger passes images and supported shared files into the workflow. * **Check a request against its PDF.** Hover over a field in a request and the matching value lights up in the PDF beside it. Works on searchable PDFs, up to the first 100 pages. [Requests](https://docs.lleverage.ai/run-operations/request-inbox) * **Edit line items cell by cell.** In Request Input and Request Decision forms, click a cell in an item list to change it. **Enter** saves, **Escape** cancels. [Request Input](https://docs.lleverage.ai/build-and-improve/automate/human-handoffs/request-input-page) * **Retry a failed Agent response.** A failed Agent response has a **Retry** button that runs your last message again. ### Improvements * **Agent reports in your style.** HTML reports the Agent makes use the Lleverage look, and your organisation's branding when it is set. * **Faster and richer Agent HTML.** Short summaries show straight in the conversation; richer reports with tabs open as a file in a preview. * **Teams conversations reach project connections.** An Agent conversation in Teams that isn't pinned to a project can use connections from the projects you have access to. [Agent in Microsoft Teams](https://docs.lleverage.ai/run-operations/agent/agent-in-microsoft-teams) * **Project API tokens follow their creator.** A Project API token stops working when the person who created it leaves or loses access to the project. **Action needed:** replace tokens owned by someone who is leaving before they go. [API tokens](https://docs.lleverage.ai/administer-and-govern/control/api-tokens) * **API access is per project.** Organisation-wide API tokens are removed. **Action needed:** integrations that used one need a Project API token. [API tokens](https://docs.lleverage.ai/administer-and-govern/control/api-tokens) ### Fixes * Files uploaded in a one-to-one Teams conversation, including inline images, reach the Agent. {% endupdate %} {% endupdates %} --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.lleverage.ai/changelog/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.