In one sentence: a pull request opened by Devin is scored like any other pull request, and its Delivery points go to the people who actually did the work; Devin keeps only what no person can claim.
Why we attribute Devin's pull requests to people
When an engineer delegates a task to Devin, the pull request is created by Devin's Git identity, but the intent, the direction and the review of that work came from a person. If all of it were credited to the agent, human Delivery would drop as soon as a team adopts Devin, even though the same people are shipping the same outcomes faster. Pensero therefore treats Devin the way it treats a co-author: the value is split on the pull request itself, between the humans behind it and the agent.
This works on the artifact, not on the session. A Devin session is not scored on its own; what is scored is the merged pull request it produced.
The rules, in order
Pensero applies the first rule that gives a deterministic answer and stops there.
Human commits win. If any commit on the pull request is authored by a person, the points are split by blame exactly like a shared human pull request (see Shared work). Devin's own commits count as a co-author would.
Then co-author trailers. If every commit is Devin's but the commits carry
Co-authored-bytrailers naming people in your organisation, those people are treated as the authors of that code. Trailers naming other AI tools or bots are ignored.Then the Devin session. If nothing in Git names a person, Pensero looks at the Devin sessions linked to the pull request (all of them together, when several sessions worked on the same PR) and identifies who sent the instructions. When one person steered the session they receive the share; when several people did, an AI reviewer reads the conversation and proposes how the value was shared between them, with a written explanation you can inspect on the item page.
Whatever share no person receives stays with Devin and is reported as Agentic delivery.
What you see in Pensero
On the item page, the Delivery total is split per contributor: the people behind the pull request each hold their percentage, and the Devin agent holds the remainder (often 0%).
A person's Delivery includes the pull requests they drove through Devin; the AI Economics page reports the human share as AI-assisted and Devin's remainder as Agentic delivery.
Only humans are credited. Automations, bots and other AI tools that appear in a session or a trailer never receive a share.
When Pensero cannot recognise a person
Sometimes a session participant or co-author is not in your Pensero directory yet (a different email domain, a contractor, a name Devin only shows as a first name). Pensero does not guess and does not drop the share: it is held under that name in Lost and Found → AI Tools. Binding the name to a contributor there moves the share to that person, including on pull requests that were already scored. See Diagnosing Missing or Incorrect AI Data.
Which metrics use this rule
Delivery, Quality, Efficiency and Benchmark use the same rule. A person's metrics include the pull requests they opened and the Devin pull requests they directed.
Delivery and Quality split the value by each person's share.
Efficiency metrics (time to merge, time to approve, time to first comment, cycle time, waste rate) count the full pull request for each person who directed it. A team or the company counts it once.
Good to know
Nothing is double counted. A pull request's points are shared, never duplicated: what a person gains, Devin gives up.
Kudos. A pull request already shared with a person cannot be re-assigned with kudos, like any co-authored pull request.
Pull requests Devin's API does not report. Pensero only links a pull request to a session when Devin reports it or the pull request description carries the session link. Pull requests it cannot link are scored on Git evidence alone (rules 1 and 2).
Cost is not split. Devin's estimated cost stays on the agent identity; only Delivery is attributed to people.