LLM Wiki's configurability for custom LLM endpoints/proxies.

This issue reveals a critical limitation in LLM Wiki's flexibility: the inability to configure custom LLM request URLs. The user's attempt to integrate a "proxy model" indicates a common enterprise or power-user requirement for controlling data flow, leveraging internal LLM deployments, or optimizing costs through third-party intermediaries. A lack of configurable endpoints forces users into a rigid architecture, hindering adoption in environments with specific security, compliance, or performance requirements. For a product aiming to be an "organized, interlinked knowledge base," this inflexibility undermines its utility as a foundational tool, as it cannot adapt to diverse LLM infrastructure strategies. This represents a significant barrier to enterprise integration and broader market penetration beyond individual, default-configuration users.