syntaqxAgents are told how a commit closes an issue: on flagon-io/g1t #47 the billing session pushed its work straight to main with commits ending "(#47)", which only links the issue, so #47 stayed open after it shipped and was closed by hand. The plugin's SessionStart and subagent context (TRAILER in hooks/g1t.mjs), the work-on-issue skill's Finish step, the system prompt of sessions on Claude Managed Agents (for a repository's first commit) and the MCP server's instructions now say that a pull request's merge closes its issue, and a commit pushed straight to the default branch closes one only when its message says Closes #N (Fixes, Resolves), never with a bare (#N); the MCP instructions add that issue close with commit closes one after the fact. The Claude Code plugin guide says so. Deploy: api and integrations; the plugin ships with its next release. Checked: node --test of plugins/claude-code/test (56), cargo test -p g1t-api mcp (5), cargo test -p g1t-integrations agent_sessions (11).047ae5fHistory
- ..
- chat
- folios
- people
- team
- actions-settings.tsx
- ai.tsx
- apps.tsx
- ask.ts
- audit-export.ts
- audit.tsx
- billing.tsx
- chat-settings.tsx
- code-access.tsx
- code-overview.tsx
- emoji.tsx
- guardrails.tsx
- home-seen.ts
- home.tsx
- insights.tsx
- integrations-directory.tsx
- integrations.tsx
- layout.tsx
- member-invitations.tsx
- members.tsx
- moved.ts
- new.tsx
- onboarding.ts
- overview.tsx
- package.tsx
- packages.tsx
- people.tsx
- permissions.tsx
- personal-access-tokens.tsx
- pins.ts
- projects.tsx
- repositories.tsx
- rules.tsx
- ruleset.tsx
- runners.tsx
- secrets.tsx
- security-bypass.tsx
- security-patterns.tsx
- security-settings.tsx
- security.tsx
- settings.tsx
- soon.tsx
- statement-csv.ts
- statement-entries.ts
- team-new.tsx
- teams.tsx
- token-new.tsx
- token.tsx
- tokens.tsx
- usage.tsx
- webhooks.tsx
- workspace-overview.tsx