{"version":"2.1.310","anchor":"self-hosted-runner-child-skips-the-remote-check-in-artifacts","canonical_anchor":"self-hosted-runner-child-skips-the-remote-check-in-artifacts","heading":"Self-hosted runner sessions now take their own path for the artifacts MCP laptop entry","tier":"internal","area":"Self-Hosted Runners","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/self-hosted-runner-child-skips-the-remote-check-in-artifacts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Self-hosted runner sessions now take their own path for the artifacts MCP laptop entry\n\nSessions started by a self-hosted runner are no longer handled like other remote sessions when Claude Code sets up the artifacts MCP laptop entry\n\n**Unclear.** Whether self-hosted runner sessions now get the artifacts laptop entry or still go without it is not shown.\n\n**What**\n\nClaude Code has a step that sets up a laptop entry for the artifacts MCP server (MCP is a standard way to connect extra tools). In remote sessions, flagged by `CLAUDE_CODE_REMOTE` or `CLAUDE_CODE_REMOTE_SESSION_ID`, it leaves that entry out.\n\nSessions started by a self-hosted runner (a machine you run yourself that starts Claude Code sessions) are now checked first and take their own path, before that remote-session check.\n\n**Why**\n\nIf you run Claude Code through a self-hosted runner, these sessions now behave differently from other remote sessions at this step.\n\n- Area: Self-Hosted Runners\n- Names: `CLAUDE_CODE_REMOTE`, `CLAUDE_CODE_REMOTE_SESSION_ID`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}