Context Backend Chat

ℹ️ Support
,
1

Issue Summary: Context Chat Backend Integration in Nextcloud Talk

We are attempting to enable and test the Context Chat Backend (version 4.3.0) as part of our Nextcloud Talk AI capabilities. The backend container is successfully running and healthy, responding to http://127.0.0.1:23004/heartbeat with {“status”:“ok”}.

:white_check_mark: What’s Working:

  • context_chat_backend Docker container has been successfully launched using the official image from Package context_chat_backend · GitHub.
  • The APP_SECRET in the container matches the one used during app_api:app:register.
  • The app is now listed as enabled via occ app_api:app:list.
  • Other ExApps like summary_bot, stt_whisper2, and talk_bot_ai are already running and functioning.

:cross_mark: Issues:

  • Despite successful registration and heartbeat, the Context Chat bot does not appear or respond in Nextcloud Talk.
  • Attempting to assign the daemon using app_api:daemon:assign failed:

Command “app_api:daemon:assign” is not defined

  • There is no clear UI or CLI documentation on how to bind this app to Nextcloud Talk conversations after deployment.
  • app_api:provider:list command is missing; possibly deprecated or not available in app_api 5.0.2.

Environment:

  • Nextcloud Version: 31.0.6.2
  • App API: 5.0.2
  • Daemon Config: manual_install, port 23004, secret matched
  • URL: https://www.scalenowai.com.au:3010
  • OS: Ubuntu with root access and Docker enabled
2 Likes
2

Thanks for the detailed update. Great to hear the container is healthy and the app is enabled. The main blocker seems to be the missing app_api:daemon:assign command and unclear binding process to Talk. This might be due to changes in app_api 5.0.2. Suggest checking for updated CLI tools or schema in newer docs or reverting to an earlier working version for compatibility.

3

Thanks @hackito how to check for updated CLI tools or schema