Per-agent GitHub token and post-run authorship check

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
49/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
github, typescript
Domain
devtools, security

Research direction

Start by reading issue #127 and tracing the existing per-agent git identity, worktree run, and Inbox Problem flows. Then locate the run’s push and pull request authentication entry points and post-run commit checks. Done means agent pushes use only that agent’s GitHub token, and a commit authored as the user creates one Inbox Problem with a Fix authorship action.

Written by the indexing model from the issue text.

Description

Split from #127, whose git identity part is done (per-agent GIT_AUTHOR/COMMITTER env, worktree runs, main .git/config untouched).

Remaining:

  • A per-agent GitHub token used for that agent's pushes and PRs, with no fallback to the user's gh login.
  • After each run, check that commits made by the run carry the agent's identity, never the founder's. On a mismatch, raise an Inbox Problem with a Fix authorship action.

Acceptance: an agent run that pushes uses the agent's token; a run whose commit is authored as the user raises one Inbox Problem.

Dominant language
TypeScript
Stars
3
Forks
0
Avg merge
17h 33m
Merged PRs (30d)
163

Getting set up

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.

More from musterhq/muster-code

All issues in musterhq/muster-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.