Chatkit Container ID - Attach to existing Container in Session Creation

API
1

Is there any available method to tie ChatKit (hosted) session creation to a container ID for bash tool? This way we could prepare the container with the skills, files and whitelist for a bash agent.

Thanks.

1 Like
2

Hey @PL, totally get why you’d want that.

Right now there isn’t a way to attach a Hosted ChatKit session to an existing container ID during session creation. The session API supports things like state_variables, history, and file uploads, but there’s no container binding field exposed. You can see the full parameter list in the docs.

If you mainly need to preload config or context, passing it through state_variables is the cleanest approach. If you’re looking for a fully prepared shell environment with specific packages or filesystem state, you’ll likely want to run the shell tool in your own infrastructure using the Shell guide instead of Hosted ChatKit.

4 Likes