MangoIDE

Linux guide · MangoIDE 0.1.0

MangoIDE documentation

Install, configure and use MangoIDE on Linux

Go to downloads
01

Compatibility and requirements

The current Linux release targets 64-bit computers. Check your system before downloading.

  • x86_64 / amd64 architecture.
  • glibc (libc6) version 2.39 or newer.
  • A Linux X11 or Wayland graphical session.
  • Internet access for remote agents and tools that download dependencies.
Terminal 
dpkg --print-architecture
ldd --version

Ubuntu, Zorin OS and Debian are supported only when the installed release provides glibc 2.39 or newer. Older distributions may refuse to start this binary.

02

Install the Debian package (.deb)

This is the recommended method for compatible Ubuntu, Zorin OS, Debian and derived systems. It adds MangoIDE to the application menu.

  • Open the download page in your language.
  • Download the Debian amd64 package.
  • Open it with your software manager, or install it from a terminal with the command below.
  • Start MangoIDE from the application menu or with the mangoide command.
Terminal 
cd ~/Downloads
sudo apt install ./mangoide_0.1.0_amd64.deb
03

Use the portable archive

The archive requires no system installation, but has the same architecture and glibc requirements as the Debian package.

  • Download the portable x86_64 archive.
  • Extract it into a folder of your choice.
  • Run the executable inside the bin subfolder.
  • Keep the share folder beside the binary to preserve the icon and desktop file.
Terminal 
cd ~/Downloads
tar -xzf MangoIDE-linux-x86_64-0.1.0.tar.gz
cd MangoIDE-linux-x86_64-0.1.0
./bin/mangoide
04

First start and projects

MangoIDE always works from a clearly selected project folder.

  • Use File > New project to create or open a project.
  • Use the folder icon in the explorer to switch directories quickly.
  • MangoIDE restores the latest project and its latest conversation after restart.
  • Every new project receives AGENTS.md, agent-text and obsidian-brain.
  • Technical folders are visually separated from application code in the explorer.
05

Configure AI agents

Open Settings and then AI Agents. Use a built-in agent or add one for your provider.

  • Select Add agent.
  • Choose a clear name, provider and model.
  • Enter an API key only when required. Local Codex can use the Codex login session installed on the computer.
  • Enable an external vision module when a text model needs to analyse images.
  • Save, then select the agent and model below the chat composer.
  • Available models depend on the provider, account and installed tools. You can also enter a model identifier manually.
06

Obsidian memory and AGENTS.md

Each project has its own technical memory, stored inside the project and usable as a regular Obsidian vault.

  • ./obsidian-brain stores project bugs, fixes, technical decisions, validations and ideas.
  • AGENTS.md gives agents project rules, useful commands and the memory location.
  • Notes must relate only to the current project.
  • An external legacy brain is read-only unless you explicitly allow writing.
  • agent-text stores project conversations and attachments.

Version AGENTS.md and useful notes when they should be shared with your team. Never store API keys or secrets in these files.

07

Chat, terminal and permissions

Chat Agents combines models, attachments and progress reporting, while the terminal runs commands in the open project.

  • Single uses one agent. Multi runs bounded collaboration between selected agents.
  • Attach several files or paste a screenshot from the clipboard.
  • Follow reads, edits, commands, builds and validations in the activity timeline.
  • Choose the least permission needed. Reserve Full for work that actually needs networking or broader system access.
  • Node.js, npm, Java, Gradle, Android SDK and other tools must be installed on the host computer.
  • Use the integrated terminal to run, interrupt and inspect project commands.
08

Troubleshooting

These checks solve most installation and configuration issues.

  • “GLIBC_x.xx not found”: the distribution is too old for this binary. Upgrade it or wait for a build targeting an older glibc.
  • Package installation fails: confirm amd64 architecture and use apt to see the exact missing dependency.
  • An agent does not respond: check its provider, model, API key or local tool login.
  • npm, Gradle or another command is missing: install it on the system and restart MangoIDE.
  • A network build fails: check connectivity and select Full only when external downloads are required.
  • The agent opens the wrong folder: open the intended project in the explorer before sending the request.

Need help?

Start with the checks above. If the issue remains, send a report including your Linux distribution, its version and the full error message.

Report a bug