You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Agent Teams provides persistent Plan, Build, Test and Review workflows across coding harnesses, with a workspace panel, human approval checkpoints and restart recovery.
The manifest declares interface screenshots from the standalone plugin (no patched-client screenshots):
OVERVIEW.md describes setup, provider data access and permission limits. The source is MIT licensed.
Preparation and validation
The declared preparation command is node server/prepare.mjs. If the pinned @getpaseo/client version is absent, it runs npm ci --omit=dev --ignore-scripts --no-audit --no-fund using the committed package-lock.json. It skips installation when that version is already present to avoid pruning development tools in an existing developer checkout. Dependency lifecycle scripts are disabled.
npm run check passes (TypeScript, ESLint, Prettier and all 81 tests). A fresh Git installation from v0.1.1 on a separate test daemon reached running at the commit above. No coding-provider session was launched for this installation check.
Updated revision
Version 0.1.1 includes commit a04ce52 (native permission handling and review correction loop fixes). The fresh tagged Git installation reached running on an isolated daemon, which was then stopped. Intake still requires a maintainer to add the submission label as requested in #765 (comment).
The submission workflow was skipped because this issue has no submission label. I requested the label when creating the issue, but GitHub did not apply it; adding it afterward returns AddLabelsToLabelable permission denied for my account.
Could a maintainer add submission to trigger intake? The tagged source, interface images and installation validation are in the issue body. Thank you.
@ssime-git, I closed the recovered older PR #1401, because your replacement submission was already published through #767. Nothing further is needed for this older submission.
Activity
ssime-git commentedon Oct 19, 2026
The submission workflow was skipped because this issue has no
submissionlabel. I requested the label when creating the issue, but GitHub did not apply it; adding it afterward returnsAddLabelsToLabelablepermission denied for my account.Could a maintainer add
submissionto trigger intake? The tagged source, interface images and installation validation are in the issue body. Thank you.github-actions commentedon Oct 28, 2026
@ssime-git, your submission is ready for review: #1401
paseo-bot commentedon Oct 28, 2026
@ssime-git, I closed the recovered older PR #1401, because your replacement submission was already published through #767. Nothing further is needed for this older submission.