I'd like to connect Buda to a Feishu group so colleagues can ask it to work on documents and other materials directly.
For example, one person might ask it to edit an article while another asks it to organize a spreadsheet. If someone then says 'continue' or 'change the second item,' how does it know which task they mean?
When several people are using it, is it better to talk in the group or have everyone message the bot privately?
Messages from several people in the same Feishu group reach the Buda Agent through that group's conversation context. The sender name helps readers, but a later “continue” or “change the second item” does not reliably identify whether it refers to the article or spreadsheet task. Do not assume the Agent automatically creates a separate Session per group member.
For independent work, have each person message the Agent privately and start a new Session for each distinct task. Put the reviewed handoff files in the shared space Drive when others need them. Keep the group for a task that people intentionally work on together, or for status updates that name a task and link the relevant file: “Continue task A, the article at this path,” rather than just “continue.” A group Session also does not create a separate permission boundary for private Drive materials.
The Sessions and Tasks guide explains the context boundary. Is the group mainly for one shared project, or as a single intake channel for unrelated requests? The Chinese discussion covers the same choice.
Sign in to join the discussion. Reading is always open; you only need an account to post.
Sign inI'd like to connect Buda to a Feishu group so colleagues can ask it to work on documents and other materials directly.
For example, one person might ask it to edit an article while another asks it to organize a spreadsheet. If someone then says 'continue' or 'change the second item,' how does it know which task they mean?
When several people are using it, is it better to talk in the group or have everyone message the bot privately?
Messages from several people in the same Feishu group reach the Buda Agent through that group's conversation context. The sender name helps readers, but a later “continue” or “change the second item” does not reliably identify whether it refers to the article or spreadsheet task. Do not assume the Agent automatically creates a separate Session per group member.
For independent work, have each person message the Agent privately and start a new Session for each distinct task. Put the reviewed handoff files in the shared space Drive when others need them. Keep the group for a task that people intentionally work on together, or for status updates that name a task and link the relevant file: “Continue task A, the article at this path,” rather than just “continue.” A group Session also does not create a separate permission boundary for private Drive materials.
The Sessions and Tasks guide explains the context boundary. Is the group mainly for one shared project, or as a single intake channel for unrelated requests? The Chinese discussion covers the same choice.
Sign in to join the discussion. Reading is always open; you only need an account to post.
Sign in