Looking at the issue, I think the most constructive approach is to suggest concrete use cases that support the feature request while also proposing a more practical alternative to a "fake" API key.

Use cases that support this feature:

CI/CD pipeline testing - running automated tests against PandaWiki without needing a real LLM provider key
Frontend-only development - UI/UX developers shouldn't need to configure model providers just to test page rendering, editor behavior, or navigation flows
Offline/demo environments - showcasing PandaWiki in air-gapped or conference demo setups where external API calls aren't feasible

Implementation suggestion (alternative to fake key):
Instead of a shared fake API key (which could cause confusion when users accidentally use it in production), consider adding a built-in "Development Mode" toggle in the admin settings. When enabled:

AI search/QA returns mock responses (e.g., "This is a simulated response for development purposes")
AI creation inserts placeholder content
All AI features function without external API calls

This approach:

Eliminates the risk of fake keys leaking to production
Provides consistent behavior across all developers
Can be extended later to support configurable mock response templates for more realistic testing

The mock mode could be toggled via environment variable (PANDAWIKI_DEV_MODE=true) or through the admin panel, making it easy to enable/disable without code changes.

Uh oh!

[功能建议] 提供开发用API Key #1795

Description

Activity

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions