Skip to main content
@ourguide-ai/agent is published to GitHub Packages as a restricted package. Every install is authenticated — there is no anonymous access, even to read. Complete these four steps once per project, plus once for every environment that builds your app.
Already have access and a token configured? Skip to the quickstart.

​
1. Request package access

Ask Argide to grant your GitHub account read access to the package. Nothing below works until that is done — an account without access gets a 404, not a permission error. Contact support@argide.ai with the GitHub username or organization that needs access.

​
2. Create a personal access token

Create a classic personal access token with the read:packages scope at github.com/settings/tokens.
GitHub Packages does not accept fine-grained tokens. It must be a classic token, or authentication fails.

​
3. Point the scope at GitHub Packages

Add an .npmrc to your project root:
.npmrc
This routes only the @ourguide-ai scope to GitHub Packages. Every other dependency still comes from the public npm registry.
npm, pnpm, and Yarn Classic all read .npmrc. Yarn Berry uses npmScopes in .yarnrc.yml instead.

​
4. Export the token wherever you install

The ${GITHUB_TOKEN} above is expanded from the environment at install time, so set it everywhere an install runs — your shell, your CI jobs, your Docker builds, and any platform that builds the app for you (Vercel, Netlify, Amplify, and similar).
Keep the token out of source control. Because .npmrc references ${GITHUB_TOKEN} rather than the token itself, the file stays safe to commit — but if you paste a literal token in, add .npmrc to your .gitignore.

​
Troubleshooting

​
Next steps

Quickstart

Initialize the SDK, claim a session, and run your first task