# Channel Select

**URL:** <https://community.interop.io/t/channel-select/698>\
**Category:** io.Connect Desktop\
**Created:** [September 13, 2026, 7:07pm UTC](https://community.interop.io/t/channel-select/698 "2026-09-13T19:07:26Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![toni.petrov](https://yyz2.discourse-cdn.com/flex028/user_avatar/community.interop.io/toni.petrov/32/17_2.png) [@toni.petrov](https://community.interop.io/u/toni.petrov)\
**Post date:** [September 14, 2026, 9:47am UTC](https://community.interop.io/t/channel-select/698/2 "2026-09-14T09:47:22Z")

</div>

Hi, can you make sure the Channels API is enabled in the initialization config - something like:

```auto
const config = { channels: true };
const io = await IODesktop(config);

```

It will help if you can also share:

1. Which demo applications are you using?

2. Are the apps in Workspace or standalone?

You can temporarily enable logging by adding `"logging": true` under`"details"` app json.

Try again and check the application log:

> [@Understanding logs in io.Connect](https://community.interop.io/t/understanding-logs-in-io-connect/36#p-43-application-specific-logs-10):
>
> People talk about flashy frameworks, IDEs, and now AI copilots as the ultimate tools for developers. But I think logs hide real superpowers that we often overlook. They’re like truth serum you give to your apps, and they will reveal their secrets. Because they track every action, error, and alert, digging into logs can save you from embarrassing bugs and help you catch issues before they crush end-users’ systems. Logs provide valuable insights into a program’s activities. Typically, logs offer …

---

_[View the full topic](https://community.interop.io/t/channel-select/698)._
