Just released Magma v0.2 which moves all configurations incl. all previously hard-coded prompt parts into your vault, so everything can now be easily adapted to your needs from within Obsidian.

The user guide was updated accordingly.

Users who already created a Magma vault with v0.1 can migrate it with:

$ mix magma.vault.migrate

Changelog

Hi everyone,

A lot has happened in the years since the last version. After this project had become practically obsolete with the rapid progress of LLMs, the rise of coding agents has made many of the original challenges acute for me again, prompting me to pick this up once more.

Magma v0.3 marks a fundamental reorientation of the project. I’ve redesigned it as a Prompt IDE for this new era.

I’ve removed the complex artefact system in favor of a much simpler, more flexible workflow.

What’s new in v0.3:

• Coding Agent Integration: New link resolution styles like :at_file_ref (e.g., @"path/to/file.md") ensure compatibility with the syntax used by coding agents.
• Structured Sessions: A new Magma.Session document type designed for multi-turn conversations. It provides an explicit, document-based record of your exchange, keeping your project context organized and modular.
• Automated Response Import: A workflow to automatically import agent responses (especially tested with Claude Code) directly back into your Obsidian vault.
• Standalone CLI: Thanks to Burrito, Magma now ships as a standalone binary for macOS and Linux. No Elixir installation is required to use the CLI tool.

GitHub: GitHub - marcelotto/magma: An IDE for prompts · GitHub
User Guide: Introduction — Magma v0.3.2