Skip to content

Feature Request: llama.cpp local endpoint support + multiple segmenters for multi-language #20

Description

@IllIIllIlllIIl

Hi, thank you for creating VectFox—it's a great idea and very useful for SillyTavern memory.

I have two feature requests related to my setup and language usage:

  1. Support for llama.cpp local endpoint
    Right now VectFox supports VLLM and Ollama backends.
    My use case is
  • Main roleplay model: runs on GPU, uses most of my VRAM
  • Embedding/summarization model: I want this to run only on CPU/RAM

Because of that, llama.cpp is ideal for me: it allows small embedding models to run fully in RAM, without touching VRAM, so I can keep all VRAM reserved for the main RP model.

Feature request:

Add support for llama.cpp local endpoints as a backend option for VectFox.

This would be very helpful for users who need strict VRAM separation between RP models and vector/summarization models.

  1. Multi-language support: allow using multiple segmenters
    On the settings page, the Multi-language support section currently lets me choose either Intl.Segmenter or Jieba WASM (TW dict)

My roleplay chats are a mix of Traditional Chinese and English, often in the same conversation.

For this kind of mixed-language usage, it would be ideal if VectFox could:

  • Either use multiple segmenters at the same time (e.g. Intl.Segmenter + Jieba TW),
  • Or provide a way to define per-language / per-field segmenter behavior.

Right now having to choose only one segmenter is a bit limiting for mixed Traditional Chinese + English scenarios.

If these are technically feasible, I think they would make VectFox much more flexible for multilingual roleplay setups and VRAM-constrained environments.

Thank you again for your work on this project!

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions