Reporting for tracks and labs now lives in one place. Instead of separate reporting sections per content type, you'll find a single Reporting section in the left menu that covers all your content.

🗂️See all your content in one set of reports

The Reporting section includes Activity, Users, Sessions and Logs. Each report shows tracks and labs together, so you can see how all your content performs without switching between pages. Use the Tracks and Labs filters to narrow the results to specific content.

The reports work the same way as before – the same metrics, filters and CSV exports. CSV exports include both content types.

⏱️Review your sandbox usage in the Usage report

The Usage report is now part of the Reporting section and available to all teams. Use it to see how many sandboxes your content started, how long they ran, and how much of your Hot Start capacity was used or left unclaimed. You can filter by date, track, invite, landing page, tag or author, and export the results to CSV.

The Usage report covers tracks only for now.

Learn more in our Reporting documentation.

We’ve released two new invite settings that let you decide exactly when end users can start your content and when their access ends. We’ve also added time zone selection to Hot Start scheduling.

🔒 Let end users start content only when your live event begins

Live Event invites have a new setting: Lock content until event starts. Until now, end users could start the content up to 24 hours before the event. With the setting on, end users can still open the invite, register and see the content. They can only start playing it once the event begins, based on the start date and time set on the invite. This keeps end users on your session plan, and your Hot Start pool isn’t used up before the session starts.

Team members with access to the invite (instructors, content creators and owners) can still play the content from the invite, so your team can troubleshoot and get ready for the session.

The setting is off by default, and existing invites stay as they are.

📅 Set the date when end users lose access to the content

In the content restrictions of any invite, you can now choose from three options to set how long end users have access to the content:

• Forever – end users keep access with no end date
• For a set duration – a period that starts when each end user claims the invite
• Until a specific date – one date and time, in the time zone you select, that applies to everyone no matter when they joined

This date is separate from the event schedule, so access can end at any point you choose. After that date, end users can no longer start the content.

🌍 Schedule Hot Start pools in your end users’ time zone

When you create a Hot Start pool, you can now pick the time zone you’re planning in. The selector starts on your current time zone, and you can search for any other one. The pool’s start and end times follow the time zone you select. A tooltip next to the scheduler explains how this works.

🎉 We’re excited to launch the AI Assistant for content creators in Labs 2.0! Start new content from a short description, or open the assistant on existing content and ask for changes – the sandbox, the instructions and the checks, built with you right inside the editor. ✨ The AI Assistant works with your team’s own Anthropic API key, so your team stays in control of your AI account, limits and spend.

Create new content from a short description
Go to Create lab → With AI, describe what you want, and choose a duration and audience level. The assistant opens on a new lab and starts building it while you watch. When it’s done, you keep chatting to shape it.

Improve existing content by asking
Open the AI Assistant next to the editor and ask in plain language: add a chapter, rewrite a page, add a quiz, tighten the instructions or refresh anything out of date. You can also ask questions about your content, like what it covers or where the gaps are.

Share screenshots and files to debug or build faster
Attach a screenshot, diagram, PDF or text file to your message. Take a screenshot of an error in your lab and ask the assistant what went wrong, or share an architecture diagram and have it build the matching sandbox. The assistant can also save an attachment into your content, for example as an image on an instruction page.

Set up the full hands-on environment
The assistant configures the sandbox for you: containers, virtual machines, Kubernetes clusters, terminals, code editors, web app tabs and cloud accounts on AWS, Google Cloud and Azure.

Get tasks with automatic checks, plus quizzes
The assistant writes tasks with their setup, check, solve and cleanup scripts, so learners’ progress is checked automatically. It also creates quizzes with single-choice, multiple-choice, text and numeric questions.

Let the assistant test your content
Ask the assistant to play through your content. It runs a real session on your draft and reports which page, task or quiz broke, so you can fix it before learners ever see it.

Review every change before you publish
Everything the assistant does goes into your unpublished draft. After each request, you get a summary of what was added, updated and removed, with links to each change and a full before-and-after view. Nothing reaches your learners until you click Publish.

Connect your own Anthropic API key
To use the AI Assistant, your team needs its own Anthropic API key. A team owner adds the key once under Settings → API keys, and all AI usage is billed to your Anthropic organization. Your key is encrypted, tied to your team and never shown again after saving.

Read more about the AI Assistant and Anthropic API Key support.

Get the AI Assistant for your team 🚀
To have the AI Assistant enabled, contact your Customer Success Manager or our Support team 💬 – we’ll guide you through the setup.

🖼️ Image builder: your own VM images, built and versioned in Instruqt

If your content needs a VM with tools pre-installed, you no longer have to install them in a setup script every time a sandbox starts. With the image builder you start from one of Instruqt's base images, install and configure what you need in a live editor, save checkpoints along the way, and publish the result as a versioned image that's private to your team. Reference it in your sandbox config as your-team/image-name:v1 and your content boots with the work already done.

Already have an image? Import it from Google Cloud or upload a disk file and it lands in your catalogue ready to use. Read more

🔔 Webhooks for Labs 2.0

Webhooks are now supported in Labs 2.0. You can receive events in your own systems when a session starts, a sandbox is provisioned or a participant completes a task, without polling the API. Endpoints are configured under Settings, where you choose the events you want to receive and can verify deliveries in the Logs tab.

Read more

🪵 Logs: stream them in the CLI, export them for debugging

The Logs page already shows everything that happens while your content runs – provisioning, setup scripts, task checks, warnings and errors. Two additions:

Logs in the CLI. instruqt lab logs my-team/my-lab streams events live in your terminal. Filter with --severity, --since, --session, --search, or --ref to watch a specific branch. For example: instruqt lab logs my-team/my-lab --ref feature-branch --severity ERROR.

Export what you see. Download the current view as JSON or copy it to the clipboard – filters apply, so you export exactly what's on screen. Each event has a copy icon too. This is useful when you want to paste a failing run into an AI assistant and ask what went wrong.

Read more

✅ Test your content from the command line

instruqt lab test simulates a participant going through your content end to end: it starts a sandbox and runs the setup, check and solve scripts for every task, so you know it works before anyone opens it. It's the same idea as instruqt track test, now for Labs 2.0. Read more

🛠️ Improvements and fixes from your feedback

Some highlights from the recent 2.0 changes that have been delivered:

• Service tabs can be opened in a new window
• Tab titles and tab order are respected when content plays
• The terminal uses the full tab width and reflows when you resize
• The integrated editor saves your edits automatically
• Changes pushed through git are played straight away, without a manual publish
• Terraform resources in the sandbox can reach the registry
• Insert Google Slides and PDFs in your instructions, and use code groups in the visual editor
• A "Recent changes" timeline and a conflict resolution flow for git-connected content
• All repository branches available in the ref pickers
• Validation errors now lead straight to the identified issue
• Warning for unsaved changes before you publish
• Faster concurrent starts on AWS

Thank you for the feedback.
We are actively working on more updates based on feedback and releasing new features for 2.0. 

We've shipped a few improvements we're excited to share. Here's what's new.

📎 Share PDFs and ZIPs in live event chat

Running a live, instructor-led event? You can now share PDF and ZIP files directly in the event chat, alongside the images already supported. It's an easy way to hand attendees reference docs, scripts or supplementary materials – they access the file right from the chat, without leaving Instruqt. Attachments up to 25 MB. Read more.

📊 See your Hotstart pools status at a glance

The Hotstarts page has a new column showing Configured / Ready / Claimed counts for each pool, right next to the Status column. You can see how many sandboxes are configured, ready and claimed without opening every pool, which makes monitoring during an event much quicker.

🔍 Full pool names on hover

Hover over a pool name on the Hotstarts page and the full name appears, so longer names are easy to read in the table. Read more about both improvements for Hotstarts.

⚡ Container-based content starts faster with image caching

We've rolled out container image caching across our infrastructure. A container can now start running while the rest of its image is still downloading, instead of waiting for the full pull to finish. On average, this cuts image pull time by up to 63%. You'll notice the biggest difference on large and complex images, such as a full IDE environment or a database engine. Small, lightweight containers were already quick to start.

Caches are per region, so the first pull of an image in a region runs at normal speed and later pulls benefit. Images with empty or duplicate layers aren't eligible for caching – the docs explain how to check yours. Read more

🎨 A refreshed look – now with light and dark mode

We've been giving pages across the app a visual refresh, including API Keys, Webhooks and the LTI interface, with more pages updated throughout:

Choose Light, Dark or System under Appearance in the account menu at the bottom left of the navigation. This is part of the groundwork as we get ready for the official release of Instruqt Labs 2.0. 🚀

Curious what's coming with Labs 2.0?

There's a lot more on the way. Join us for the hands-on event on September 29th to see it in action.

As an Instruqt customer, you're invited as a VIP. Register with the link below and we'll ship you the 2026 swag kit – canvas tote, insulated bottle, notebook and gel pen, and the holographic Iggy sticker. There are 150 VIP invitations and a limited number of kits, so register asap - sign up here.

Your usage limits now cover both Tracks and 2.0 Labs in one place.

"Track Limits" is now "Session Limits." This is mainly a facelift: the protection you already rely on to guard against runaway usage hasn't changed, it now simply applies across everything you publish, whether it's a Track or a 2.0 Lab, all managed from a single view.

What it is

Session limits are guard rails on how many sessions can be started for a piece of content. Without them, anything public or embedded on a website could be launched an unlimited number of times, running up cost and inviting abuse. Limits cap that across four dimensions: per calendar month, per rolling month, per IP address per hour, and concurrent plays per IP.

It's one system covering both content types. There's a single Session Limits area, and in the management table every piece of content carries a tag showing whether it's a Track or a 2.0 Lab. One page, one set of controls, built for both.

Why it matters

• Protects against runaway usage and cost, for all your content, Tracks and 2.0 Labs alike.
• One place to manage everything. Tracks and 2.0 Labs live together, distinguished by a tag.
• Safe to share widely. Publish or embed content with confidence that there's a ceiling in place.

How it works

Set a team wide default that applies across all your content, then override the limits for individual items when you need to. The management table lists every Track and 2.0 Lab together, with current values and a content type tag for each.

Limits are checked the moment a new session starts. A session that would exceed a limit is blocked, and the learner sees an informative message rather than a raw error.

Key capabilities

• Four configurable limit dimensions: calendar month, rolling month, IP address per hour, and concurrent plays per IP
• A team wide default with per content overrides
• One management table for both Tracks and 2.0 Labs, each marked with a content type tag
• Limits enforced at session start
• A clear, informative message for learners who hit a limit

Good to know

If you know Track Limits, you already know Session Limits. Same protection, same controls, now unified under one name and one view across Tracks and 2.0 Labs.

Recently we've shipped a set of improvements focused on running live, instructor-led sessions, creating better invites, and managing Hot Start pools – plus a refreshed set of best-practice guides. Here's what's new.

Export chat history from live sessions

You can now download the chat from a live session directly from the Live dashboard, so the questions, feedback, and follow-up items your participants share stay with you after the session ends. The download covers both messages to all users and direct messages, including attachments – each with the sender's name and timestamp – and stays available for 30 days after the session. See Analyze activity after the event for details.

Hot Start improvements

We made two changes to make Hot Start pools easier to manage day to day:

• Expiration date and time now show in the Hot Starts overview. The pools table has a new "Expiration date & time" column, so you can see at a glance which pools are about to expire and decide whether to pause, extend, or delete them – right from the overview.
• Clearer guidance on locked fields. A Hot Start pool's Scope and Target type define its structure and are set at creation. A new tooltip now surfaces this directly on the fields at both creation and edit time, making how these settings work clear at a glance. Documentation updated as well.

A richer invite creation experience

Public invite description now supports full rich text formatting: bold, italic, numbered lists, bullet points, and links. That means you can lay out agendas, prerequisites, schedules, and key details in a clear, structured way. The invite creation form has been redesigned to match. The title and description fields now stretch to the full width of the page, giving you far more room to write and review your content as you build the invite.

New updated guides & videos

We've reworked our best-practice documentation for running events and instructor-led training. If you deliver live sessions or manage Hot Start pools, these are worth a read:

• Hot Starts best practices, by event type. Hot Start setup isn't one-size-fits-all – a 50-person live workshop needs a different configuration than an always-on embedded lab. This guide gives pool sizing, provisioning lead time, auto-refill, and cleanup recommendations for each event type: self-paced on-demand training, live workshops, webinars, multi-day training, conference hands-on sessions, booth/expo demos, and single-prospect demos. Each comes with a worked example and the common mistakes to avoid. We’ve also created a video with the recommended setups for every event type.
• Understanding Hot Start settings. If you're setting up a Hot Start pool and aren't sure what each option does, this short video walks through the key settings in the creation flow – what each one controls and why it matters – so you can configure your pool with confidence.
• Workshop best practices, now with a step-by-step checklist. Our workshop guide has been restructured into a clear, phased checklist – pre-event planning (IP limits, Hot Start pre-provisioning), invitations and access control, day-of facilitation, and post-event wrap-up – so you can follow it end to end and not miss a step.
• Running live Instructor-Led Training sessions. A new comprehensive guide to the full ILT flow: getting ready for the session, facilitating the event, troubleshooting, and following up afterwards. It covers the three formats teams run most – on-site, virtual, and conference workshops – with the spe

We've made improvements to the Manage Hot Starts page to help you focus on what matters most.

See Running and Provisioning pools first

When you open the Hot Starts page, you'll now see your Running and Provisioning pools at the top by default - the ones that matter most to your day-to-day. Inactive, deleted, and all other statuses are still available - just use the filter on the page to select the ones you need to add to the view.

Your filter selections now stay put

And once you've set those filters the way you want them, they'll stay that way. Your selections are saved and stay persistent in your session on the device - so you don't have to reapply them every time you come back to the page.