Claude Code artifacts are great in-session. internalpage turns outputs into private team pages.

Claude Code artifacts are useful when a coding session produces something easier to review as a page than as terminal text: annotated diffs, dashboards, timelines, design options, or lightweight interactive views. Anthropic currently documents Claude Code artifacts for Team and Enterprise plans, with the page updating as the session continues.

• Fast visual output from a Claude Code session
• Good for reviewing work in progress inside the same Claude organization
• Useful when the artifact is tightly tied to the active agent session
• Private by default, with organization sharing available to the creator

internalpage is for artifacts that should outlive the agent session and behave like part of your internal knowledge surface: a generated report, private API reference, release note, Markdown runbook, or review page that people can revisit from a stable URL.

• Publish HTML, Markdown, and OpenAPI files from a CLI, script, CI job, or local agent
• Render Markdown into readable private docs
• Render OpenAPI specs with ReDoc, Swagger UI, or Scalar in read-only mode
• Keep a stable viewer URL while replacing the underlying version
• Use custom domains such as docs.company.com without moving authoritative DNS to Cloudflare

Claude Code artifact sharing follows the Claude organization boundary: Anthropic says the creator can share with people in that organization and cannot make the Claude Code artifact public. internalpage instead focuses on page-level sharing through Google Workspace sign-in, selected-email access, or workspace-wide links outside a Claude session.

• Share with a Google Workspace domain or selected email addresses
• Let viewers authenticate with their existing Google account
• Avoid requiring viewers to be in a Claude organization
• Use the same access model on internalpage URLs and custom-domain URLs

A page that updates with an active Claude Code session is ideal for live investigation and review. A separately published internalpage artifact is better when a generator, CI job, or person should replace a finished file behind a known slug and keep that destination in docs or incident workflows.

• Use Claude Code artifacts for session-native review and exploration
• Use internalpage for repeatable publishing from agents, CI, and local scripts
• Use internalpage when the URL should be referenced from tickets, runbooks, Slack, or docs
• Use internalpage when the page needs a custom domain or viewer access outside Claude

Ask Claude Code to save the final HTML or Markdown artifact in the repository or an ignored output directory. Review it locally, then publish it with a stable slug from your authenticated CLI environment.

• Keep the internalpage token outside the prompt and generated file
• Review external links, embedded data, and scripts before publishing
• Use the same slug for later versions of the same team asset

npx @internalpage/cli publish ./claude-report.html --slug claude-report

Start with Claude Code artifacts when the page is part of a live Team or Enterprise coding session and every viewer belongs to the same Claude organization. Publish with internalpage when the artifact needs a Google-based audience, selected-email grants, a custom domain, or a repeatable file-to-page workflow.

• Live session context and organization-only review: Claude Code artifact
• Stable Google-protected viewer URL: internalpage
• Repeat updates from scripts or CI: internalpage
• Both can be used in sequence when a live investigation becomes a durable report