---
id: post/demiliani-com/12644
type: post
title: "Dynamics 365 Business Central: debugging agent sessions."
summary: The 2026 release wave 1 (runtime 17.0) of AL Language extension adds the ability to debug agent sessions directly from Visual Studio Code. Developers can attach to agent sessions running on cloud sandboxes or on-premise servers using new launch configurations and can inspect what agents are doing by connecting via user security ID or session ID.
tier: community
language: en
tags:
  - debugging
  - agent sessions
  - al language
  - visual studio code
  - runtime 17.0
  - launch configuration
system: copilot
review:
  state: reviewed
  by: opus
  at: "2026-10-08T01:58:47.777Z"
  flags: []
generated:
  at: "2026-10-08T01:26:53.141Z"
  pipeline: 0.2.0
  prompts:
    extract-post: 1
  input_hash: 9f8dc2b61939a5fc62e37aae962a12b108f3693cec5c7a1a4cf59bc5499b2d5f
evidence:
  - kind: blog
    url: https://demiliani.com/2025/10/21/dynamics-365-business-central-debugging-agent-sessions/
    title: "Dynamics 365 Business Central: debugging agent sessions."
    date: "2025-10-21"
    commit: null
    t: null
    quote: null
  - kind: blog
    url: https://demiliani.com/2025/10/21/dynamics-365-business-central-debugging-agent-sessions/
    title: "Dynamics 365 Business Central: debugging agent sessions."
    date: "2025-10-21"
    commit: null
    t: null
    quote: With this 17.x release it's possible to attach to agent sessions and debug the AL code they are executing.
  - kind: blog
    url: https://demiliani.com/2025/10/21/dynamics-365-business-central-debugging-agent-sessions/
    title: "Dynamics 365 Business Central: debugging agent sessions."
    date: "2025-10-21"
    commit: null
    t: null
    quote: You can also use the sessionId parameter to connect to the specific agent session.
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
post_id: "12644"
source_id: demiliani-com
source_name: Stefano Demiliani
url: https://demiliani.com/2025/10/21/dynamics-365-business-central-debugging-agent-sessions/
published_at: "2025-10-21T06:20:40.000Z"
author: Stefano Demiliani
full_text: false
words: 194
quotes:
  - text: With this 17.x release it's possible to attach to agent sessions and debug the AL code they are executing.
    why_it_matters: "This is the core capability introduced: developers can now actively debug agent code execution, which was not possible before."
  - text: You can also use the sessionId parameter to connect to the specific agent session.
    why_it_matters: "Shows the granular control available: developers can target exact agent sessions rather than just the next one encountered."
code_objects_mentioned: []
systems:
  - copilot
  - development
  - platform
versions_mentioned:
  - 2026 release wave 1
  - runtime 17.0
preview:
  embeddable: true
  frame_url: https://demiliani.com/2025/10/21/dynamics-365-business-central-debugging-agent-sessions/embed/
  image: https://demiliani.com/wp-content/uploads/2025/10/agentdebug_01.png
  image_alt: null
  image_w: 1086
  image_h: 692
  site_name: Stefano Demiliani
  favicon: https://demiliani.com/wp-content/uploads/2022/09/sd_wordpress_logo.png?w=32
  probed_at: "2026-10-07T11:51:29.066Z"
---

# Dynamics 365 Business Central: debugging agent sessions.

[Read the post](https://demiliani.com/2025/10/21/dynamics-365-business-central-debugging-agent-sessions/) · Stefano Demiliani (Stefano Demiliani, MVP) · 2025-10-21 · 194 words · tier community · reviewed (checked by Opus)

> The 2026 release wave 1 (runtime 17.0) of AL Language extension adds the ability to debug agent sessions directly from Visual Studio Code. Developers can attach to agent sessions running on cloud sandboxes or on-premise servers using new launch configurations and can inspect what agents are doing by connecting via user security ID or session ID.

## Key points

- AL Language extension runtime 17.0 introduces debugging support for agent sessions in Business Central
- New client type Agent has been added along with two launch configurations for cloud and on-premise debugging
- Developers can attach to specific agent sessions using security ID or sessionId parameter
- Snapshot debugging stops at the next identified agent session for inspection and monitoring

## Quotes

- "With this 17.x release it's possible to attach to agent sessions and debug the AL code they are executing." (This is the core capability introduced: developers can now actively debug agent code execution, which was not possible before.)
- "You can also use the sessionId parameter to connect to the specific agent session." (Shows the granular control available: developers can target exact agent sessions rather than just the next one encountered.)

## Context

- Features: agent session debugging, launch configurations, snapshot debugging, client type Agent
- Versions: 2026 release wave 1, runtime 17.0

Source: Stefano Demiliani, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.