langgenius / langgenius/syncless-issue

bug: Agent has no awareness of the current Owner's identity in delegated tasks

Open
#279 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
No language data
Stars
4
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Summary

In a delegated (downstream) task, the Agent has no awareness of who the current Owner is. This causes logical confusion in the conversation — the Agent cannot distinguish its own Owner from other project participants, leading to misrouted messages and redundant clarification loops.

Reproduction

Task URL: https://syncless-web.iqiy.cn/tasks/15b91f4f-98f6-45a9-bc6a-4a30f74316d5

Participants:

  • Owner of the downstream task: Peter.han (peter.han@dify.ai)
  • Upstream task owner: 张游
  • Workspace: 中集集团集星杯AI大赛公共区

Steps:

  1. A downstream task "从zip创建或更新技能" is delegated to Peter.han's representative Agent.
  2. Peter.han (the Owner) sends a message in the task: "请你问一下他,到底是什么问题,我需要更详细的问题描述。"
  3. The Agent, instead of understanding Peter.han as its own Owner giving instructions, misidentifies the situation and sends a task.send to the upstream owner 张游 asking Peter.han for details — reversing the direction entirely.
  4. When Peter.han corrects it with "不是,问上游!", the Agent still shows confusion about who "上游" is vs. who it is talking to.

Expected Behavior

The Agent in a task should always know:

  1. Who its Owner is — the person who holds the task seat (Peter.han in this case).
  2. Who it is receiving instructions from — messages in the task from the Owner are commands, not third-party references.

The Agent should never confuse the Owner's identity with that of other project participants, and should never need to "ask Peter.han" when Peter.han is the one already talking to it.

Actual Behavior

  • Agent treated Peter.han as an external party and sent a message to the upstream task asking Peter.han for information.
  • Agent could not correctly identify the upstream task owner vs. its own Owner.
  • Conversation looped with the Agent re-asking questions already answered by the Owner.

Impact

Downstream delegated tasks become unusable when the Agent cannot ground itself in the correct Owner identity. The confusion compounds in multi-party project workflows where multiple owners are present.

Version

Client: 0.0.72

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked task reproduction and trace the delegated-task conversation involving Peter.han and 张游. Done means the Agent identifies the task Owner, treats that Owner's messages as instructions, distinguishes the upstream owner correctly, and no longer reverses message direction or repeats answered questions.

Written by the indexing model from the issue text.

Assessment

Domain
ai, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.