Replies: 55 comments 116 replies
Can I enable the AI in an unofficial way now in my instance?The answer is yes. Steps for those using provided compose file:1. create a JSON config at
{
"$schema": "https://github.com/toeverything/affine/releases/latest/download/config.schema.json",
"copilot": {
"enabled": true,
"providers.openai": {
"apiKey": "your key",
"baseUrl": "open-ai-compatitable.example.com"
}
}
}2. restart your host docker compose up -dSteps for custom deployment:1. create a JSON config {
"$schema": "https://github.com/toeverything/affine/releases/latest/download/config.schema.json",
"copilot": {
"enabled": true,
"providers.openai": {
"apiKey": "your key",
}
}
}2. Mount or Copy the config file to your instance 3. import the config node --import ./scripts/register.js ./dist/data/index.js import-config ./path/to/config.json4. restart your host |
|
I try to set up today but get import-config not found issue. any ideas? |
|
pull the latest image |
|
I tried this configuration to connect to my ollama server but it didn't work {
"$schema": "https://github.com/toeverything/affine/releases/latest/download/config.schema.json",
"copilot": {
"enabled": true,
"providers.openai": {
"apiKey": "ollama",
"baseUrl": "http://IP:11434/v1"
}
}
} |
How can I configure DeepSeek? How to set up the model. Moreover, in the 0.21.2 management panel, the AI function cannot be activated.
|
|
That why I called the solution in #11691 (comment) is "unofficial". to configure AI functionality in Admin panel is still work in progress. Regarding using DeepSeek, it's concurrently not supported yet, but I think it will be available with AI admin panel together |
|
Hello! Thanks for the tips for selfhosted instance Will there be AI support for local workspace? |
|
You can only use simple actions in local workspace like random chat, translation. The actions with context awareness, for example embedding, can not be used with local workspaces, because the server doesn't know the content of your local workspace |
|
好像仍然有10次的使用限制，我使用自己的 API key 进行配置，并在openrouter后台看到了使用记录，但是affine中的AI仍然只能使用10次 |
|
Wow, it's really possible! In the account settings, click on modify, and you can see the options, thank you very much 🙏 |
|
You're welcome :) |
你使用的是什么模型，我这边这个管理员面板的 AI 按钮无法开启，是禁用状态 |
|
@ssly 使用OpenAI兼容的API以及正确的apikey没有问题，服务启动时会检测API的可用性，可以查看日志。如果没有办法开启AI可能是配置有误。理论上还支持其他的AI provider，具有可用性可查看对应的源代码。 |
|
请问，怎么更换掉系统原来的提示词。每次提问都带一大串自我介绍提示词 |
|
I created for myself a small server between Affine and Gemini or OpenRouter, who provides free API keys. Not sure if this allowed here in this chat. |
|
Excellent, I used your method. Successfully used the model of Gemini and openrouter on AFFiNE 0.21.4 |
|
Edit: Figured it out: I am following your guide from your repo to be able to use OpenAI with the AFFINE version of 0.21.4 which is the latest stable version and the connection is not working for some reason. Any help would be appreciated. Below are all my files:
{
"$schema": "https://github.com/toeverything/affine/releases/latest/download/config.schema.json",
"server": {
"name": "Affine"
},
"copilot": {
"enabled": true,
"providers.openai": {
"apiKey": "my-not-exist-api-key",
"baseUrl": "http://affine-copilot-fix:5000"
}
}
}
name: affine
services:
affine-copilot-fix:
container_name: affine-copilot-fix
user: "1000:1000"
build:
context: ./affine-copilot-fix
dockerfile: Dockerfile
volumes:
- ./logs:/app/src/logs
env_file:
- .env
environment:
- CREATE_LOG=True
- OPENAI_API_KEY=${OPENAI_API_KEY}
- OPENAI_BASE_URL=https://openrouter.ai/api/v1 # https://openrouter.ai/api/v1/
- OPENAI_MODEL=openai/o4-mini # Or any openrouter model
ports:
- 5000:5000
networks:
- proxy
affine:
image: ghcr.io/toeverything/affine-graphql:${AFFINE_REVISION:-stable}
container_name: affine_server
ports:
- '${PORT:-3010}:3010'
depends_on:
redis:
condition: service_healthy
postgres:
condition: service_healthy
affine_migration:
condition: service_completed_successfully
volumes:
# custom configurations
- /opt/docker/affine/.affine/self-host/storage:/root/.affine/storage
- /opt/docker/affine/.affine/self-host/config:/root/.affine/config
env_file:
- .env
environment:
- REDIS_SERVER_HOST=redis
- DATABASE_URL=postgresql://${DB_USERNAME}:${DB_PASSWORD}@postgres:5432/${DB_DATABASE:-affine}
restart: unless-stopped
networks:
- proxy
affine_migration:
image: ghcr.io/toeverything/affine-graphql:${AFFINE_REVISION:-stable}
container_name: affine_migration_job
volumes:
# custom configurations
- /opt/docker/affine/.affine/self-host/storage:/root/.affine/storage
- /opt/docker/affine/.affine/self-host/config:/root/.affine/config
command: ['sh', '-c', 'node ./scripts/self-host-predeploy.js']
env_file:
- .env
environment:
- REDIS_SERVER_HOST=redis
- DATABASE_URL=postgresql://${DB_USERNAME}:${DB_PASSWORD}@postgres:5432/${DB_DATABASE:-affine}
depends_on:
postgres:
condition: service_healthy
redis:
condition: service_healthy
networks:
- proxy
redis:
image: redis
container_name: affine_redis
healthcheck:
test: ['CMD', 'redis-cli', '--raw', 'incr', 'ping']
interval: 10s
timeout: 5s
retries: 5
restart: unless-stopped
networks:
- proxy
postgres:
image: postgres:16
container_name: affine_postgres
volumes:
- /opt/docker/affine/.affine/self-host/postgres/pgdata:/var/lib/postgresql/data
environment:
POSTGRES_USER: ${DB_USERNAME}
POSTGRES_PASSWORD: ${DB_PASSWORD}
POSTGRES_DB: ${DB_DATABASE:-affine}
POSTGRES_INITDB_ARGS: '--data-checksums'
# you better set a password for you database
# or you may add 'POSTGRES_HOST_AUTH_METHOD=trust' to ignore postgres security policy
POSTGRES_HOST_AUTH_METHOD: trust
healthcheck:
test:
['CMD', 'pg_isready', '-U', "${DB_USERNAME}", '-d', "${DB_DATABASE:-affine}"]
interval: 10s
timeout: 5s
retries: 5
restart: unless-stopped
networks:
- proxy
networks:
proxy:
driver: bridge
external: true |
|
any issues or questions, please open in my repo. |
|
@boom404 Hi, how do I customize the prompt word. Otherwise every request comes with a long string of prompt words: |
this is hard coded in Affine. |
|
Since recently, I get this error message when trying to use it: My relevant {
"$schema": "https://github.com/toeverything/affine/releases/latest/download/config.schema.json",
"server": {
"name": "myname",
"host": "affine.myname.de",
"https": true
},
"copilot": {
"enabled": true,
"providers.openai": {
"apiKey": "sk-proj-...",
}
}
}Any ideas? |
|
I experienced the same problem. The AI chat in the sidebar wasn't working, but the normal "Ask AI" in documents was fine. I've turned off the "world icon" in the chat sidebar. But, i'm using my own Affine Copilot Fix, because I want to use Gemini - nevertheless, the problem should be maybe the same.
|
|
Same issue here using the latest stable self hosted docker version. |
|
if you enable the websearch feature, by toggling the |
|
Which docker version does your solution work with? I have used stable and canary version and none work with your configuration and would like to know the version that works to see the difference in code from before to now to know how to fix this and possibly have a Github PR made with a solution. |
|
the latest stable should work fine |
|
Is there a way to define which model to use? |
|
not available yet |
|
I use openresty to redirect the requests to deepseek and the config.json |
I think this method is good, but after trying it, it still gets |
|
Copilot provider [openai] registered. Gemini might be because of the network (configured in the background). Openai is configured in the background and config.json. It still prompts that it is unavailable. |
|
Is there a usage cap when using AI on self hosted even when using my own AI Token???? |
|
nope |
|
Even tho I set the config.json (validated if its set with cat config.json in root/.affine/config) and set unlimited ai usage, I get this error when trying to send a message: |
|
Same here, but I think it's because of the unlimited_Copilot Feature. When I set my config.json and imported it into node, everything was working until the quota cap. Once I set unlimited_copilot, the quota was gone, but I get this error. So i think they have hardcoded something that tries to use a specific ai provider once somebody has purchesed the ai feature. I mean it makes total seance cause once you purchased, affine is responsible for providing the ai.. |
|
currently AFFiNE binds actions to specific provider or models, because the models capabilities distinguish, like some model only process text and return text, some can read from pictures, some can generate pictures. You may also hear GPT-4o, GPT-o1, gemini-2.0, etc. They are all for different purposes. And what's even worse, some advanced models was considered to be used in AFFiNE are not available for all, like openai accounts. the error this is the main reason we didn't tell AFFiNE AI as self-host ready and can only be used as experimental feature. |
|
Coudn't we allow users to congigure which model to use instead of hard coding, eg: openai/openai-4.1-mini, etc... and just mention that the LLM endpoint must be openai compatible. This helps, eg: when using liteLLM that give an openai endpoint for whichever model is configured behind it. ofcourse for a selfhosted instance the user/hoster will need to know if they should use a text only or a multimodal model. There are cheaper and even free models, that can be used this way, eg: gpt4.1-mini instead of gpt-4.1 (which is hardcoded and more expensive) or Mistral-small which is free and multimodal. |
|
definitely. We are on it but it will take some time to finish the refactory. Please be patient then. |
|
I am trying to set up the latest stable and beta for AI running on a self-hosted cloud. After several tries I got this: Is it possible to resolve this? |
|
Hope AFFiNE to support custom providers(ollama, deepseek, ...) |
|
Hey guys, since ./scripts/register.js got removed, I can't import my config for the ai anymore with node --import ./scripts/register.js ./dist/data/index.js import-config ./path/to/config.json. Did anybody get ai to work on 0.22.2? |
facing same issue |
|
@forehalo |
|
npm run cli import-config /root/.affine/config/config.json |
|
Any updates? |
|
I'd like to get some info as well. The deep AI Integration is one of the main features of affine and I would love to see that for self-hosted as well. |
|
Still getting the same error as mentioned above in self hosted, after 7 days.
|
Although version 0.25.1 has been released, it still does not support custom providers such as Ollama and DeepSeek. Is there an estimated timeline for when this feature will be available? |
|
Ollama provides an openAI compatible API endpoint no? setting the baseUrl to your ollama url doesn't work? |
Thats the point, it does not handle openai api without a proxy that modifies requests and responses like the ones discussed in the thread |
|
it does now, with the oldApiStyle:true parameter: |
|
I have AI working. Am I correct in assuming the names in the UI will not change regardless of what I put in the AI config? They will always say gemini? |
|
Web Search failed in Affine AI option and I am using gemini api key |
|
ty |
|
Does anyone know how to integrate openrouter in place of open ai? |
|
chat and text generation was working for me the other day, but now nothing works. cursed application. anyway, at the very least make sure you are using the correct model names. open router needs the company prefixed. so gpt-4 would be openai/gpt-4 and so on in config settings. use the 'copy' button in the respective model's model page on open router |
|
What's going on here? 
The pricing page for self-hosted AFFiNE doesn't even mention AI usage limits. 😢 
|
|
You can switch off this restriction in the settings, then you can make infinite AI requests. It's typical nonsense from Affin again.
|
|
I don't know if it's the same for you, but after struggling for a few days, I went to the admin settings > Accounts on the far right, click the 3 dots under "actions" for your username > edit > then select UnlimitedCopilot. Everything worked fine for me after that. I hope it's as easy for someone else as it was for me. |
|
It worked, thank you so much! 🙌🏻 |
|
Same, thanks a lot ! |
|
thanks |
Can people share their working configs?someone post a working open router config, a litellm, a ollama, etc. then we can put them at the top in the main message @forehalo this thread is getting long with lots of conflicting information |
|
Here, I use LiteLLM to proxy third-party models, employing a reverse proxy method (cloudflare worker or caddy server) to proxy the Gemini API. I didn't cover all the scenarios. That can only solve the basic problem of using third-party models in Affine selfhost. |
|
I wonder if everyone is still interested in this topic. I’ve made an important discovery (with the help of GitHub Copilot): by simply setting a single environment variable— The article has been updated, and I hope it will be helpful for everyone https://torchtree.com/en/post/affine-selfhost-ai-configuration/ 
|
|
Setting This issue persists with self-hosted LLMs like vLLM and Ollama, where the logs from |
|
Alright looks like you need a model with tools functionality. Switching to Qwen 3 30b works. |
|
Correct, I'm using "qwen2.5:7b-instruct". Still looking for a working embedding model. |
Are Image Inputs working for you? |
|
Apparently not, AI thinks my images are white. |
Images just give me an error :/ |
|
Hi
I still have the error message about the limit call and what is strange is that in the provider selector I only have Gemini, no other element or model to select. I don't see any error in the logs What am I missing ? |
|
Agreed however I will not complain. AFFiNE has great features in a free application so I can accept to run a SQL command from time to time |
|
I think i activated 7 | unlimited_copilot in the database. |
|
For deepseek-chat:
Works in v0.25.7 |
|
Where to add 'self hosted=true' in Docker compose? Looking forward to your reply! @methodx |
|
@auto-fly it's docker-compose.yaml. |
|
I tried everything in this thread and Copilot still not working. Even using an OpenAI key after a fresh install I get I'm using LiteLLM and is working well with other tools, and the config for the openai provider set at I even used a proxied URL and AFFiNE is not calling it when I configure it as openai baseUrl... How can this be debugged to at least find the URL used? |
|
same issue the only error i get is |
|
|
|
Why has the "unlimited AI" toggle disappeared from the self-hosted admin panel since 0.27.x? The AI provider configuration also seems to be missing from the config now. My AI setup had been working fine for months and just broke because of these changes. My profile shows that I've reached my AI limits, even though I had enabled unlimited AI before. Is anyone else experiencing this issue? |
|
Same here |
|
user_features no longer has any unlimited_copilot entry — only administrator remains — and ai_workspace_byok_configs (the new workspace-scoped provider/API-key table introduced around 0.27.x) is completely empty, 0 rows, for any workspace. selfhosted is set true. So this isn't a hidden UI, and it isn't a subscription/quota bug either — it's that 0.27.3 replaced the old global "unlimited AI" user-feature + config.json provider setup with a per-workspace BYOK mechanism, and the migration didn't backfill the old config into the new table. The old admin toggle and config fields are gone because the feature they controlled doesn't exist anymore in this form; the new mechanism expects providers to be registered directly in ai_workspace_byok_configs, and mine (and apparently everyone else's) just came out empty after upgrading. Given that, the fix isn't to restore the old toggle — it's to re-register the provider through whatever UI now writes to ai_workspace_byok_configs (looks like it moved to a workspace-level AI settings screen rather than the global admin panel). Might be worth flagging as a migration bug upstream, since anyone upgrading through 0.27.3 with an existing self-hosted AI setup is going to hit this same silent data loss. |
|
So, how exactly do I get ai integrations to work? All I get is Despite having configured openai provider. |
and others
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Progress
All reactions