I won’t be sharing anymore—I think it’s enough just for my own use. Sorry to bother everyone.
50GB of test data? 
Seriously? 
What’s the difference between this and m365 copilot2api?
There should be a difference, right?
For example, it wouldn’t be like my project, where bugs are crammed in haphazardly.
And the UI is also very different…
Hey, this keeps happening whenever I use your project, and switching to other models doesn’t help either. Have you encountered this problem?
Could it be that Microsoft has started imposing restrictions? But this is a new account.
Check out my post…
I messed something up when I made changes 
1 Like
It might be better to go back to the previous version.
Can your new project read local files now? I’m deploying it with Docker on the server.
The inability to read files is probably an agent compatibility issue. Codex does have problems; switching to dsh fixes it, and it’s not as slow as cc either. 
I still mostly use codex; I’m currently trying out this new project.
If it really doesn’t work, you can start a sub-agent and let the sub-agent do the reading. After all, this is being reverse-proxied from a web page, so it’s normal for tools to run into issues.
1 Like
Awesome 
When deploying the service to use it as your own relay, is this key format incorrect? I can’t access the model.
This is not a problem.
I tried it out, and it’s much easier to use than yours. Haha, but don’t just give up and stop updating yours either.
I had Claude handle the entire deployment, then manually added the account pool. It’s working perfectly now—the only issue is that the first token takes 8 seconds. I’m not sure whether it’s a server or network problem.
We still need to address the tool loop issue. It’s caused by synchronization problems and will be fixed later.