[Feedback Here] Agent Team Now Available on LobeHub

[rivertwilight]

Agent Team brings together multiple AI agents, each with their own expertise, to collaborate on your conversations. Richer discussions, diverse viewpoints, and solutions you wouldn't get from any single agent.

https://github.com/user-attachments/assets/671d06ac-4739-4601-8d92-4ccedbeece3e

Try it Out

For Self-hosting Users

Set FEATURE_FLAGS =+group_chat env to enable group chat in your self-hosted version.

For Cloud Users

Still in internal test and not generally available. But you are still able to try out via invitation.

Send us your email to join the beta tester list, and you will able to access it in the https://lobechat.com once we added your email.

Feedback Welcome

This is still a very early stage so your feedback is really important to us. Feel free to comment here or send feedback in our Discord server.

---

Update: We decide to rename this feature to Agent Team.

[lobehubbot]

👀 @RiverTwilight

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible. Please make sure you have given us as much context as possible.

[lobehubbot]

Labeled as group chat feedback thread. Community feedback is welcome here for the new Group Chat feature.

[sxjeru]

Thank you for developing such a practical feature. Here are a few suggestions:

1. Suggest allowing "Add Member" to create a new assistant that only displays within the group, avoiding clutter in the left assistant list.
2. ~~Suggest adding a "Stop Group Chat" button, as currently on the web version you can only forcefully stop the group chat by refreshing.~~ (This is for cases where the task list is not displayed)
3. After the host lists the task list, do you need to manually click the "Start Group Chat" button in the upper right? This may need guidance, or you could also add a start task button on the task list.
4. The host model seems unable to be readjusted on the settings page. (Relatively serious issue)

---

This comment was translated by Claude.

Original Content

感谢开发如此实用的功能,这边稍微提几点建议。

1. 建议添加成员允许新建助手,且该助手只在群内显示,避免打乱左侧助手列表。
2. ~~建议添加停止群聊按钮,目前网页端大概只能靠刷新强行停止群聊运行。~~(这个针对没有列出任务列表的情况)
3. 主持人列出任务列表后,是不是需要手动点击右上开始群聊按钮,这个可能需要引导,或者在任务列表上也添加开始任务按钮。
4. 主持人模型似乎无法在设置页重新调整。(比较严重)

[SAnBlog]

1. When setting different models for each group member, after configuration, the different group members incorrectly display as the last member's set model. However, during group chat, it becomes the originally set model - there's a bug in the display.
2. If one model encounters an error during response, it will automatically retry for all members, resulting in multiple error messages appearing.
3. After an error occurs, no topic error appears. It seems to be in a temporary topic, but after deleting the entire group, the chat information appears on the home page of "Just Chat" and cannot be deleted no matter what.

---

This comment was translated by Claude.

Original Content

1.每个群员设置不同模型,设置后不同群员错误显示成最后一个成员设置的模型,群聊时又成了设置的模型,显示方面有 bug。 2.如果一个模型回复时报错后,会自动对全部成员进行重试,导致多个报错信息出现。 3.报错后没有出现话题报错,好像是再临时话题里,但是把整个群组删掉后,该聊天信息出现在随便聊聊的首页中,怎么删都删不掉

[hedeqiang]

There will be empty content, I'm using aihubmix

---

This comment was translated by Claude.

Original Content

会有空内容,我使用的是 aihubmix

[hedeqiang]

Additionally, it outputs in an infinite loop and won't stop

<author_name_do_not_include_in_your_response>Product Manager</author_name_do_not_include_in_your_response> <author_name_do_not_include_in_your_response>Product Manager</author_name_do_not_include_in_your_response> <author_name_do_not_include_in_your_response>Product Managers/author_name_do_not_include_in_your_response>

---

This comment was translated by Claude.

Original Content

另外会无限循环输出 ,不会停止

<author_name_do_not_include_in_your_response>Product Manager</author_name_do_not_include_in_your_response> <author_name_do_not_include_in_your_response>Product Manager</author_name_do_not_include_in_your_response> <author_name_do_not_include_in_your_response>Product Managers/author_name_do_not_include_in_your_response>

[mamachanko]

Just upgraded, enabled group chat and started using it. After a few rounds of debate between two agents, I am getting the following error:

{
  "shape": {
    "message": "Failed query: insert into \"messages\" (\"id\", \"role\", \"content\", \"reasoning\", \"search\", \"metadata\", \"model\", \"provider\", \"favorite\", \"error\", \"tools\", \"trace_id\", \"observation_id\", \"client_id\", \"user_id\", \"session_id\", \"topic_id\", \"thread_id\", \"parent_id\", \"quota_id\", \"agent_id\", \"group_id\", \"target_id\", \"message_group_id\", \"accessed_at\", \"created_at\", \"updated_at\") values ($1, $2, $3, default, default, default, $4, $5, default, default, default, default, default, default, $6, $7, $8, default, $9, default, default, default, default, default, default, default, default) returning \"id\", \"role\", \"content\", \"reasoning\", \"search\", \"metadata\", \"model\", \"provider\", \"favorite\", \"error\", \"tools\", \"trace_id\", \"observation_id\", \"client_id\", \"user_id\", \"session_id\", \"topic_id\", \"thread_id\", \"parent_id\", \"quota_id\", \"agent_id\", \"group_id\", \"target_id\", \"message_group_id\", \"accessed_at\", \"created_at\", \"updated_at\"\nparams: msg_NztPyxU1LQefbg,assistant,...,google/gemini-2.5-flash,openrouter,0dadda88-e8e8-406f-a7d8-313e67b642fb,cg_kfRPbRelUxW5,,msg_ao6J0vW4HjxZc3",
    "code": -32603,
    "data": {
      "code": "INTERNAL_SERVER_ERROR",
      "httpStatus": 500,
      "path": "message.createMessage"
    }
  },
  "data": {
    "code": "INTERNAL_SERVER_ERROR",
    "httpStatus": 500,
    "path": "message.createMessage"
  },
  "meta": {
    "response": {},
    "responseJSON": [
      {
        "error": {
          "json": {
            "message": "Failed query: insert into \"messages\" (\"id\", \"role\", \"content\", \"reasoning\", \"search\", \"metadata\", \"model\", \"provider\", \"favorite\", \"error\", \"tools\", \"trace_id\", \"observation_id\", \"client_id\", \"user_id\", \"session_id\", \"topic_id\", \"thread_id\", \"parent_id\", \"quota_id\", \"agent_id\", \"group_id\", \"target_id\", \"message_group_id\", \"accessed_at\", \"created_at\", \"updated_at\") values ($1, $2, $3, default, default, default, $4, $5, default, default, default, default, default, default, $6, $7, $8, default, $9, default, default, default, default, default, default, default, default) returning \"id\", \"role\", \"content\", \"reasoning\", \"search\", \"metadata\", \"model\", \"provider\", \"favorite\", \"error\", \"tools\", \"trace_id\", \"observation_id\", \"client_id\", \"user_id\", \"session_id\", \"topic_id\", \"thread_id\", \"parent_id\", \"quota_id\", \"agent_id\", \"group_id\", \"target_id\", \"message_group_id\", \"accessed_at\", \"created_at\", \"updated_at\"\nparams: msg_NztPyxU1LQefbg,assistant,...,google/gemini-2.5-flash,openrouter,0dadda88-e8e8-406f-a7d8-313e67b642fb,cg_kfRPbRelUxW5,,msg_ao6J0vW4HjxZc3",
            "code": -32603,
            "data": {
              "code": "INTERNAL_SERVER_ERROR",
              "httpStatus": 500,
              "path": "message.createMessage"
            }
          }
        }
      }
    ]
  },
  "name": "TRPCClientError"
}

The error persists for every attempt to regenerate a response. All other chats are working fine.

[antonkulaga]

I think what will be the most helpful is to have both multiple human and AI users. As there are many team-usecases where several users want to have shared chat

[arvinxx]

@antonkulaga good idea, and we will try to do in the team feature

[htdohk]

Desktop works fine but mobile can not group each characters together。。。 v1.138.5

[rivertwilight]

@htdohk Currently you can only access to this feature on desktop device.

[hajajmaor]

@htdohk Currently you can only access to this feature on desktop device.

Why is that? Why limit this great feature to desktops only? This is a group chat; no special layout is required.

[shog86]

Deployed on Vercel, encountered this message after enabling the group chat feature, unable to chat

[\n {\n "code": "invalid_type",\n "expected": "string",\n "received": "null",\n "path": [\n "topicId"\n ],\n "message": "Expected string, received null"\n }\n]

---

This comment was translated by Claude.

Original Content

Vercel部署的,开了群聊功能后遇到这个消息,聊不起来

[\n {\n "code": "invalid_type",\n "expected": "string",\n "received": "null",\n "path": [\n "topicId"\n ],\n "message": "Expected string, received null"\n }\n]

[rivertwilight]

@htdohk Currently you can only access to this feature on desktop device.

Why is that? Why limit this great feature to desktops only? This is a group chat; no special layout is required.

We do want to this works on mobile but it takes extra time I'm afraid we don't have yet because currently we focus on the core system.

[shog86]

Just upgraded, enabled group chat and started using it. After a few rounds of debate between two agents, I am getting the following error:

{
  "shape": {
    "message": "Failed query: insert into \"messages\" (\"id\", \"role\", \"content\", \"reasoning\", \"search\", \"metadata\", \"model\", \"provider\", \"favorite\", \"error\", \"tools\", \"trace_id\", \"observation_id\", \"client_id\", \"user_id\", \"session_id\", \"topic_id\", \"thread_id\", \"parent_id\", \"quota_id\", \"agent_id\", \"group_id\", \"target_id\", \"message_group_id\", \"accessed_at\", \"created_at\", \"updated_at\") values ($1, $2, $3, default, default, default, $4, $5, default, default, default, default, default, default, $6, $7, $8, default, $9, default, default, default, default, default, default, default, default) returning \"id\", \"role\", \"content\", \"reasoning\", \"search\", \"metadata\", \"model\", \"provider\", \"favorite\", \"error\", \"tools\", \"trace_id\", \"observation_id\", \"client_id\", \"user_id\", \"session_id\", \"topic_id\", \"thread_id\", \"parent_id\", \"quota_id\", \"agent_id\", \"group_id\", \"target_id\", \"message_group_id\", \"accessed_at\", \"created_at\", \"updated_at\"\nparams: msg_NztPyxU1LQefbg,assistant,...,google/gemini-2.5-flash,openrouter,0dadda88-e8e8-406f-a7d8-313e67b642fb,cg_kfRPbRelUxW5,,msg_ao6J0vW4HjxZc3",
    "code": -32603,
    "data": {
      "code": "INTERNAL_SERVER_ERROR",
      "httpStatus": 500,
      "path": "message.createMessage"
    }
  },
  "data": {
    "code": "INTERNAL_SERVER_ERROR",
    "httpStatus": 500,
    "path": "message.createMessage"
  },
  "meta": {
    "response": {},
    "responseJSON": [
      {
        "error": {
          "json": {
            "message": "Failed query: insert into \"messages\" (\"id\", \"role\", \"content\", \"reasoning\", \"search\", \"metadata\", \"model\", \"provider\", \"favorite\", \"error\", \"tools\", \"trace_id\", \"observation_id\", \"client_id\", \"user_id\", \"session_id\", \"topic_id\", \"thread_id\", \"parent_id\", \"quota_id\", \"agent_id\", \"group_id\", \"target_id\", \"message_group_id\", \"accessed_at\", \"created_at\", \"updated_at\") values ($1, $2, $3, default, default, default, $4, $5, default, default, default, default, default, default, $6, $7, $8, default, $9, default, default, default, default, default, default, default, default) returning \"id\", \"role\", \"content\", \"reasoning\", \"search\", \"metadata\", \"model\", \"provider\", \"favorite\", \"error\", \"tools\", \"trace_id\", \"observation_id\", \"client_id\", \"user_id\", \"session_id\", \"topic_id\", \"thread_id\", \"parent_id\", \"quota_id\", \"agent_id\", \"group_id\", \"target_id\", \"message_group_id\", \"accessed_at\", \"created_at\", \"updated_at\"\nparams: msg_NztPyxU1LQefbg,assistant,...,google/gemini-2.5-flash,openrouter,0dadda88-e8e8-406f-a7d8-313e67b642fb,cg_kfRPbRelUxW5,,msg_ao6J0vW4HjxZc3",
            "code": -32603,
            "data": {
              "code": "INTERNAL_SERVER_ERROR",
              "httpStatus": 500,
              "path": "message.createMessage"
            }
          }
        }
      }
    ]
  },
  "name": "TRPCClientError"
}

The error persists for every attempt to regenerate a response. All other chats are working fine.

Also see this on v.next.29

It takes very very long to end up getting no response