Give the agent a real task.
Read and edit files, run terminal commands, and work through changes on your machine. The agent acts with your user permissions—not inside a guaranteed sandbox. Review its access and changes.
AI coding workspace · persistent project memory
Your work has
a history.
Keep it.
Write code with an agent that can use your project’s saved decisions, constraints and working procedures. Choose the model. Inspect the memory. Take the records with you.
Windows & Linux · Your hardware · Your model-provider account
The reason behind the code
“Why did we choose SQLite?”
Decision · current
Keep the prototype local. It needs to run without a database service.
Earlier proposal · superseded
Use a hosted database from day one.
Constraint · still applies
Export must work without contacting our servers.
Inspect saved decisions, constraints and working procedures directly in your project workspace.
01 Work on your own machine02 Inspect what was saved03 Export without asking permission
Less reconstruction. More work.
The next session should not
start with your entire backstory.
Aedelgard brings coding tools and stored project history into one workspace. The goal is simple: make the reasoning behind yesterday’s work available when you continue today.
Keep more than the final answer.
Save decisions, constraints and reusable procedures. Inspect records and correct outdated facts. A project heading helps scope recall; it is not a confidentiality boundary between clients.
Change the model, not the archive.
Use a supported provider or compatible local model without discarding saved history. Models still differ in reasoning, recall and tool use. Portable records do not guarantee identical behaviour.
Ownership that does something
Your records.
Your next move.
Memory is useful only if you can examine it, correct it and recover it. You should not need to stay with one model—or with Aedelgard—to keep the history of your work.
Inspect the architecture →- Inspect the source records
Review stored memory and the history of changed facts. Saving a record is not the same as recalling it reliably.
- Export a portable archive
The built-in ZIP export includes portable memory and its knowledge graph, not provider credentials. The ZIP is unencrypted: store it privately and verify restoration on a compatible installation.
- Choose where inference goes
With a remote model, context goes directly to your provider under its policies. A compatible local model handles inference on your machine. Optional cloud backup carries encrypted memory, not model inference.
A clear offer, not a lock-in
Local work first.
Backup by choice.
Aedelgard runs locally on your own machine. Your memory stays local-first and completely yours, with zero platform subscription required. Connect your own model provider (or run local models offline) — provider charges remain directly between you and your provider.
Paid cloud backup is a separate service. Review its price, renewal and cancellation terms before buying. Keep your cloud key safe: we cannot recover it, though losing it does not erase an existing local copy.
Review cloud service details →
A mind that is wholly yours.
Never wake a stranger.
That is the ambition. The practical work is keeping useful history—inspectable, correctable, and yours to carry forward.