ElimuLink Code

ElimuLink inside VS Code, for students and lecturers.

• Chat: open the ElimuLink icon in the side bar and ask any coding question. Sign in with your ElimuLink account.
• Knows your project: it reads the open folder (file list, README and setup files, the open file, open tabs and any file you name) and the Problems list.
• Edits files: proposed changes show an Apply button; you see a before/after comparison first.
• Runs things: commands (run, install, test), opening localhost, searching the project, Git commit and push, GitHub pull requests and deploys appear as cards with a Run, Open or Search button. Nothing happens until you press it.
• Agent mode: switch on Agent beside + and describe a task. ElimuLink plans, edits several files, runs the project, reads errors, fixes and runs again until it works, runs the tests before saying done, and can build a whole small app and open it in the browser. Stop any time; Undo all changes at the end.
• Connected services: "ElimuLink: Connect a service" for Render (services, logs, deploys, restart), Supabase (is it awake, read tables), Firebase (your CLI sign-in) and any API key. Keys stay on this laptop.
• Right-click your code: Explain, Fix or Improve this code. With nothing selected, the whole file is used.
• Command Palette: "ElimuLink: Safety rules", "ElimuLink: Ask before every command again", "ElimuLink: Sign in / Sign out".

Your data

To answer, ElimuLink Code sends these to the ElimuLink server (elimulink-api.onrender.com), which uses Google Gemini to write the answer:

• your question and the recent conversation;
• the project's file list and the contents of the files it reads (README and setup files, the open file, open tabs, files you name), the Problems list, and, when you ask about Git, your changes;
• the output of commands you ran from the chat, and files or pictures you attach;
• your ElimuLink account name and email if you sign in.

It never reads or sends .env and key files, and it hides anything that looks like a key, token or password in command output. Keys for connected services stay on your laptop and are never sent. ElimuLink Code collects no analytics or tracking of its own. ElimuLink does not train AI models on your code. While ElimuLink uses the free tier of Google Gemini, Google may use what is sent to improve its services, so do not send anything confidential. See the ElimuLink Privacy Policy and User Agreement for how the service stores data.

Safety rules

1. Nothing runs by itself. Every command, page, push and deploy waits for your tap on Run or Open.
2. "Always allow" is offered only for safe, everyday commands (run, test, build, install, git status/diff/log). Push, deploy, delete and anything with a key never get it.
3. Risky commands (deleting files, git push --force, git reset --hard, dropping a database, formatting a drive, piping a download into a shell, sudo) get a red warning and need a second tap. ElimuLink is told never to suggest them unless you asked.
4. Git push, pull requests and deploys always ask again, even if you allowed something else.
5. Keys and passwords never go to the AI. .env and key files are never read or sent; command output is cleaned of anything that looks like a key, token or password before ElimuLink sees it. Never paste a key into the chat: keep it in .env.
6. Commands run only inside your open project folder, in a terminal named "ElimuLink" that you can see and stop (click the bin icon or press Ctrl+C).
7. Pages: localhost opens straight away inside VS Code; any other website asks first.
8. File changes are shown as a before/after comparison and saved only when you press Apply.
9. Long-running commands (dev servers) keep running in the ElimuLink terminal; ElimuLink only reads the first lines.
10. You are in charge: you can stop any command, undo any change with Ctrl+Z or Git, and sign out at any time.

Agent mode (the Agent switch) 11. Before a task starts, ElimuLink asks once. "Start" lets it edit files in your project and run safe commands (install, run, test, build) by itself for that task only. "Ask me at every step" shows every change and command first. 12. Even in an agent task it always asks before pushing, deploying, deleting, opening other websites, calling an API that changes data, or restarting a service. Dangerous commands still get the red warning. 13. It never writes .env or key files, and stops after 15 steps. Press the square Stop button at any time. 14. "Undo all changes" at the end puts every file back the way it was before the task (new files are deleted). 15. It runs the tests (or the app) before saying a task is done.

Connected services (Render, Supabase, Firebase, any API) 16. Keys are typed once with "ElimuLink: Connect a service" and kept in VS Code's secret store on this laptop. The AI never sees them: it asks for an action, VS Code does the call, and only the cleaned result goes to the AI. In API requests the AI writes {{key:name}} and VS Code fills in the key. 17. Reading is allowed (Render services, logs and deploys; whether Supabase is awake; up to 20 rows of a table). Changing anything (restart, POST, PUT, DELETE) asks first. Reading from a new website asks once. 18. Firebase uses your own Firebase sign-in; deploys always ask. 19. Only ask for the data you need: table rows may hold students' personal information. Never paste rows with personal data anywhere public. 20. "ElimuLink: Disconnect services" removes every key from this laptop.