Sign-in, security and support

#Signing in

Open your workspace address https://name.cloud.eggent.ai and sign in with the email and password you gave at signup. The same email and password work on the billing and sync pages.

Signed up in Telegram? Send /login to the bot: it answers with a button that opens the workspace already signed in. The button works once and for 10 minutes; /login sends a new one.

Right after signup the workspace opens already signed in, through a one-time link. The link works once and for 10 minutes.

#Change login and password

Settings → General → Dashboard authentication. Enter a new login (your email or a name) and password (at least 8 characters) and save. Every other browser signed in to the workspace is signed out; this one stays in. The new details apply to the billing and sync pages too.

#Forgot the password

Press Forgot your password? on the sign-in page and enter the email the workspace is registered to. A letter comes with a link for every workspace of that address; each link works once and for an hour. Set a new password there and you are signed in, while every other browser that was signed in is signed out.

The page answers the same way whether or not it knows the address, so it cannot be used to find out who has a workspace. Nothing came? Look in spam, ask again in a few minutes, then write to support.

#Confirming your email

Right after signup a letter comes with a 6-digit code. Type it on the signup page while the workspace starts, send it to the bot if you signed up in Telegram, or press the button in the letter (it works for two days). Until then the sidebar reminds you once in a while; nothing else waits for it.

A Telegram account connected later by a link (when the agent offers to send things to Telegram) can talk to the agent at once. To also sign in with /login, it needs your word: the bot sends a letter to your address with a button to confirm.

#Language and theme

Settings → General: the interface language (English or Russian) and a light or dark theme. The language also sets which language the agent answers in by default.

#How data is protected

• Every workspace runs in its own container with its own disk. Other workspaces cannot see it.
• Eggent AI models are reached through the Eggent gateway: model providers' keys never enter the workspace.
• Your own providers' keys saved in settings are kept in a protected workspace file and never enter the chat history.
• Files the agent builds as web pages open isolated and have no access to the workspace.

#Rules for keys and passwords

The agent sees everything you write in the chat, and chat history is stored. So:

• Model keys go into Settings → Models, not the chat.
• The Telegram bot token goes into Settings → Messengers.
• MCP server tokens go into Settings → MCP.
• Do not give the agent passwords to your accounts: it cannot sign in to sites anyway.

If a secret has already ended up in a chat, delete that chat and reissue the key with the service.

#Support

• The Help button in the bottom right of the workspace — with links to support and to file sync.
• Telegram: @youriisupport.
• Email: aiiszdes@gmail.com.

Include your workspace address (name.cloud.eggent.ai) and what happened — it gets you an answer faster.

#Deleting a workspace

Write to support from the email the workspace is registered to. Before deletion, download the files you need or turn on sync with your computer: once deleted, the data cannot be recovered.