[Feature] adding multi account support like gemini 1 , gemin 2 , gemin 3

[shikooos]

Problem
for large data handling and hammering request it might blocked or denied access
Proposed solution
adding multi account support will ease and smooth pressure on one account

Alternatives considered
Any other approaches you've thought about.

Additional context
Any other info, mockups, or references.

[shikooos]

I reviewed the BrowserManager. This is the correct layer to implement multi-Gemini accounts.

Your current architecture:

BrowserManager
      |
      |
persist:gemini
      |
      |
Gemini Google Account (ONE)

The limitation is here:

gemini: {
    url: 'https://gemini.google.com/app',
    partition: 'persist:gemini',
    color: '#4285f4'
}

Electron partition = isolated cookies.

So currently:

persist:gemini
        |
        +-- cookies
        +-- localStorage
        +-- cache
        |
        Google Account A

To support:

Gemini-1
 |
 persist:gemini-account-1
 |
 Google Account A


Gemini-2
 |
 persist:gemini-account-2
 |
 Google Account B


Gemini-3
 |
 persist:gemini-account-3
 |
 Google Account C

we need to make Gemini a dynamic provider family.

---

1. Modify providers definition

Replace:

gemini: {
    url: 'https://gemini.google.com/app',
    partition: 'persist:gemini',
    color: '#4285f4'
}

with:

gemini: {
    url: 'https://gemini.google.com/app',
    partition: 'persist:gemini',
    color: '#4285f4',
    multiAccount: true
}

---

2. Add Gemini account registry

Inside constructor:

after:

this.providers = {

add:

this.geminiAccounts = {
    default:{
        id:"default",
        partition:"persist:gemini"
    }
};

---

3. Add account creation function

Add this method:

createGeminiAccount(accountId){

    if(!accountId)
        throw new Error(
          "Gemini account id required"
        );


    if(this.geminiAccounts[accountId]){
        return this.geminiAccounts[accountId];
    }


    const account={
        id:accountId,
        partition:
          `persist:gemini-${accountId}`,
        url:
          'https://gemini.google.com/app'
    };


    this.geminiAccounts[accountId]=account;


    console.log(
      '[Gemini] Created account partition:',
      account.partition
    );


    return account;
}

---

4. Modify createView()

Current:

createView(provider)

Change:

createView(provider, accountId=null)

---

Then replace:

const config = this.providers[provider];

with:

let config;


if(provider==="gemini" && accountId){

    const account =
       this.createGeminiAccount(accountId);


    config={
        ...this.providers.gemini,
        partition:
          account.partition
    };

}else{

    config=this.providers[provider];

}

---

Now:

createView(
 "gemini",
 "gemini2"
)

creates:

persist:gemini-gemini2

---

5. Change view map key

Currently:

this.views.set(provider, view);

Problem:

gemini
 |
 one view only

Change:

const viewKey =
(
provider==="gemini" && accountId
)
?
`${provider}:${accountId}`
:
provider;


this.views.set(viewKey, view);

Result:

views Map

gemini:account1
gemini:account2
gemini:account3

---

6. Modify showProvider()

Current:

showProvider(provider,bounds)

Change:

showProvider(
 provider,
 bounds,
 accountId=null
)

Then:

const viewKey =
provider==="gemini" && accountId
?
`${provider}:${accountId}`
:
provider;


if(!this.views.has(viewKey)){
    this.createView(provider,accountId);
}

---

7. Auth popup must use same partition

Current:

openAuthPopup(provider,url)

Change:

openAuthPopup(
 provider,
 url,
 accountId=null
)

Replace:

const config=this.providers[provider];

with:

let config;


if(provider==="gemini" && accountId){

 const account =
 this.createGeminiAccount(accountId);


 config={
   ...this.providers.gemini,
   partition:account.partition
 };

}else{

 config=this.providers[provider];

}

Now login goes into the correct account.

---

8. Add account switching API

Add:

getGeminiAccounts(){

    return Object.values(
       this.geminiAccounts
    );

}

and:

deleteGeminiAccount(id){

    const account=
      this.geminiAccounts[id];


    if(!account)
       return false;


    delete this.geminiAccounts[id];


    return true;
}

---

9. IPC layer

Your renderer can now call:

{
 provider:"gemini",
 account:"gemini2"
}

Example:

browserManager.showProvider(
 "gemini",
 bounds,
 "gemini2"
);

---

10. Result

After modification:

Proxima

AI Providers

Gemini
 |
 +-- Account 1
 |       persist:gemini-account1
 |       Google user A
 |
 +-- Account 2
 |       persist:gemini-account2
 |       Google user B
 |
 +-- Account 3
         persist:gemini-account3
         Google user C

The Gemini engine source I modified earlier will receive:

send(
 message,
 engine,
 attachments,
 sessionId,
 false,
 "gemini2"
)

and the BrowserManager supplies the correct cookie container.

---

Important implementation note

Do not copy cookies manually.

Electron partitions already provide the correct isolation:

partition
    |
    Chromium Storage
       |
       + cookies
       + IndexedDB
       + localStorage
       + service workers

So the clean solution is:

One BrowserView + one Electron partition per Gemini account.

This requires only:

1. BrowserManager patch (this file)
2. Gemini engine patch (previous file)
3. IPC command addition (small file)

The two large modifications are now identified. The remaining file needed is the IPC/main process handler where showProvider() and executeScript() are exposed, so the account parameter can travel from UI/API → BrowserManager.