{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiahfztp5sanabonddnerh2aalqh7yqswl3q7aedbiwlkmfzytodfe",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mhp54m6grep2"
  },
  "path": "/t/how-to-make-2-ai-vtubers-talk-to-eachother-in-vtube-studio/174490#post_6",
  "publishedAt": "2026-03-22T23:54:12.000Z",
  "site": "https://discuss.huggingface.co",
  "textContent": "Very long explanation but right now I’m thinking of making sure there is no possible for the token to switch to the other at any point in time.\n\nAlso Fixed a Connection issue where the api pop-up wasn’t working on terminal 1\n\nAlso wanna do the terminal 1 controls MouthOpen, terminal 2 controls HyoriMouth\n\nAnd keep the token files separate and use different ports since it seems very common for it to be driven into errors otherwise for some reason\n\nRight now i have a lot of conflicting code but I’ll fix it later but i do have a somewhat temporary solution for this although I’m still working on a fix\n\nAlso this:\n\nOnly use this if you intentionally want one VTS instance.\n\nterminal 1 → 8001 → MouthOpen\n\nterminal 2 → 8001 → HyoriMouth\n\nRules for this design:\n\nterminal 1 never touches HyoriMouth\n\nterminal 2 never touches MouthOpen\n\nThis also seems pretty safe to try personally later so I’ll test it later i guess As i could feed data of terminal 1 to only that openmouth and make terminal 2 only feed data into hyorimouth Despite using the same api port there would likely not being a issue with this setup",
  "title": "How to make 2 ai vtubers talk to eachother in vtube studio?"
}