mirror of
https://github.com/lobehub/lobehub.git
synced 2026-09-20 04:56:13 +08:00
191f3fe776
* 📝 docs: fix outdated content across the docs site Audited docs/ against the current codebase and fixed stale content that drifted after major refactors (Clerk/NextAuth → Better Auth, src/server → apps/server, src/{config,envs,locales} → packages/*, model-bank updates). - self-hosting/auth: mark removed NextAuth/Clerk pages with deprecation warnings; fix microsoft/zitadel alias claims and the Logto callback path - environment-variables & advanced: correct wrong defaults (S3_SET_ACL, AI_IMAGE_DEFAULT_IMAGE_NUM, index/proxy URLs), drop non-existent env vars and fictional feature flags, fix OIDC config guidance - development: update refactored paths, Better Auth, .mjs configs, remove the MSW section (msw is not a dependency) - providers & model examples: replace retired model ids with in-bank ones; fix comfyui frontmatter corruption - usage: rename Moderator→Orchestrator, GTD→Task, correct shortcut keys, channel capability tables, Feishu/Lark WebSocket mode - platform/migration: fix dead links, docker service name, npx/npm → bun EN and zh-CN pairs updated together. * 📝 docs: fix Logto callback path and AUTH_SECRET deprecation guidance - Revert Logto/Sealos callback URLs to /api/auth/callback/logto to match the runtime SSO redirectURI override - Narrow legacy auth Callout: AUTH_SECRET remains required for Better Auth; mark NEXT_AUTH_SECRET as deprecated in zh-CN * 📝 docs: refresh agent skills for locales, env, auth, and agentRun paths Align OSS agent guidance with post-refactor layout: - packages/locales/src/default + bun run i18n - packages/env/src for env schemas (@/envs alias) - spa-auth shell + src/routes/auth segments - chat agentRun/transports/hetero instead of aiChat * 📝 docs: document APP_URL as required for Better Auth base URL Self-hosted auth uses appEnv.APP_URL as baseURL, not request-header auto-detection. NEXT_PUBLIC_AUTH_URL remains deprecated. * 📝 docs: note self-host search provider setup for web search Built-in lobe-web-browsing needs no client plugin, but self-hosted servers still require SEARCH_PROVIDERS / SEARXNG_URL (default SearXNG). * 📝 docs: point feature guide welcome UI at AgentHome Opening message/questions on the agent chat page live in src/features/AgentHome, not Onboarding WelcomeMessage.
66 lines
3.0 KiB
Plaintext
66 lines
3.0 KiB
Plaintext
---
|
||
title: Using GitHub Models in LobeHub
|
||
description: >-
|
||
Learn how to configure and use GitHub's API Key in LobeHub to start
|
||
conversations and interactions.
|
||
tags:
|
||
- LobeHub
|
||
- GitHub
|
||
- GitHub Models
|
||
- API Key
|
||
- Web UI
|
||
---
|
||
|
||
# Using GitHub Models in LobeHub
|
||
|
||
<Image cover src={'/blog/assetsf117203c39294f45930785d85773c83e.webp'} />
|
||
|
||
[GitHub Models](https://github.com/marketplace/models) is a new feature recently launched by GitHub, designed to provide developers with a free platform to access and experiment with various AI models. GitHub Models offers an interactive sandbox environment where users can test different model parameters and prompts to observe the model's responses. The platform supports a range of advanced language models, including OpenAI's GPT-4o, Meta's Llama 3.1, and Mistral's Large 2, covering a wide spectrum of use cases from large language models to task-specific models.
|
||
|
||
This guide will walk you through how to use GitHub Models within LobeHub.
|
||
|
||
## GitHub Models Rate Limits
|
||
|
||
Currently, usage of the Playground and free API is subject to limits on requests per minute, daily requests, tokens per request, and concurrent requests. If you hit a rate limit, you’ll need to wait for it to reset before making additional requests. Rate limits vary depending on the model type (low, high, or embedding models). For details on model types, refer to the GitHub Marketplace.
|
||
|
||
<Image alt={'GitHub Models Rate Limits'} inStep src={'/blog/assets50607dece1bbffe80fdcbe76324ff9b6.webp'} />
|
||
|
||
<Callout type="note">
|
||
These limits are subject to change. For the most up-to-date information, please refer to the [official GitHub documentation](https://docs.github.com/en/github-models/prototyping-with-ai-models#rate-limits).
|
||
</Callout>
|
||
|
||
---
|
||
|
||
## GitHub Models Configuration Guide
|
||
|
||
<Steps>
|
||
### Step 1: Obtain a GitHub Access Token
|
||
|
||
- Log in to GitHub and navigate to the [Personal Access Tokens](https://github.com/settings/tokens) page.
|
||
- Create and configure a new access token.
|
||
|
||
<Image alt={'Create Access Token'} inStep src={'/blog/assetsc376d2e9e97f9ea9d788589f0a9e23d6.webp'} />
|
||
|
||
- Copy and securely save the generated token from the result page.
|
||
|
||
<Image alt={'Save Access Token'} inStep src={'/blog/assets9880145be3e52b8f9dcd8343cd34a6ca.webp'} />
|
||
|
||
<Callout type={"warning"}>
|
||
Be sure to store your access token securely, as it will only be shown once. If you lose it, you’ll need to generate a new one.
|
||
</Callout>
|
||
|
||
### Step 2: Configure GitHub Models in LobeHub
|
||
|
||
- Open the `Settings` panel in LobeHub.
|
||
- Under `AI Providers`, locate the `GitHub` configuration section.
|
||
|
||
<Image alt={'Enter Access Token'} inStep src={'/blog/assetse0d53ba2bfb6ba5bf33f2b8a547f4e41.webp'} />
|
||
|
||
- Paste the access token you obtained earlier.
|
||
- Choose a GitHub model for your AI assistant to start chatting.
|
||
|
||
<Image alt={'Select GitHub Model and Start Chatting'} inStep src={'/blog/assetsb6959f725c38f86053e4b07c9188d825.webp'} />
|
||
</Steps>
|
||
|
||
And that’s it! You’re now ready to start using GitHub-provided models in LobeHub for conversations and interactions.
|