Skip to content

[Improve] Tell Auto who the session owner is - #3383

Merged
daniel-lxs merged 2 commits into
developfrom
improve/auto-owner-identity
Oct 2, 2026
Merged

daniel-lxs merged 2 commits into
developfrom
improve/auto-owner-identity

Conversation

@daniel-lxs

Copy link
Copy Markdown
Member

Why

Auto compares a tool call with what the owner asked for, but it was never told who the owner is. Two things followed:

  • A request such as "assign it to me", or a plan that said "I can assign it to you", followed by a call naming the owner by name or email, asked for approval although the owner had asked for exactly that.
  • A call naming somebody else where the owner said "me" could run, because nothing showed it was a different person.

What

  • Auto is given the session owner's name and email, only when the owner sent every message in the session. In a session other people wrote in, "me" is not always the owner, so nothing is added and those sessions are judged as before.
  • Code marks which argument values are exactly the owner's name or email, so a look-alike (a longer name, another domain) is never taken for the owner.
  • The questions about what the owner asked for and what plan they agreed to say how to use this. A tool's own "who am I" result counts as the owner under another name; a document that claims who the user is does not.
  • A task's calls get the same treatment as the session agent's.

How to test

  1. Turn Auto on for a session and connect a tracker-style integration.
  2. Ask: "Which of Sam's issues are stale? Propose reassigning them to me, don't change anything yet." Then reply "yeah go ahead".
  3. The reassignment calls name your account and run without an approval card.
  4. In a fresh session ask "assign ISSUE-1 to me". A call that names a teammate asks for approval.

Unit tests cover the sender check, the exact match, and both call paths.

Auto was never told who the owner is, so it could not tell a call that
names them from one that names somebody else. A plan that said "assign
it to you" followed by a call naming the owner asked needlessly, and a
call naming a teammate where the owner said "me" could run.

Auto is now given the owner's name and email when the owner wrote every
message in the session, and code marks which argument values are exactly
that name or email, so a look-alike is never taken for the owner. A
session other people wrote in is judged as before.
@roomote-community

roomote-community Bot commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

No code issues found. See task

  • Task owner attribution can ignore a prior participant after the 20-message window (packages/db/src/lib/integration-tool-auto-task-context.ts:435).

Reviewed 951acdf

Comment thread packages/db/src/lib/integration-tool-auto-task-context.ts
Only the recent task prompts were checked, so an earlier prompt from
somebody else stopped counting once it left the history and the owner
could be named in a shared task. Senders are now checked over all of the
task's prompts, as they already were for the session.
@daniel-lxs
daniel-lxs merged commit c78cd01 into develop Oct 2, 2026
22 checks passed
@daniel-lxs
daniel-lxs deleted the improve/auto-owner-identity branch October 2, 2026 21:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant