The most important thing for a memory system is not only remember and recall or search, it is maintain, that including, merge, forget, update etc. That is how human's work.
I am on linggen.dev , that is the one make daily agent work easier.
For most apps, cross platform like Flutter or RN is the best choice. For apps highly bind on the hardware, or need better performance, usually native is better. But for vibe coding or harness coding today, if workload is not the problem, native is usually a better choice, it allows you do different thing on different platform.
same here. i usually only notice fonts when something feels off, not when it's working. the article made the hidden defaults feel a lot less arbitrary.
the hard part probably isn't search over 500k emails, it's keeping the generated wiki from becoming a second messy inbox. i'd want to see how it handles stale facts and conflicting versions of the same project. email has a lot of "this was true for two weeks in 2019" buried inside it.
Thanks for the note.
While building the context bundle, there is a tool that detect gaps in the timeline. So when you ask 'kitchen renovation', and there are emails from 2019 and 2023, the tool flags these gaps and the LLM is made aware of it. So Memento asks which of these clusters you want to track as a project.
Later while generating the wiki, LLM handles conflicts and facts that evolved over time because it has the timestamp of the messages. So it shows that in the narrative.
Wwat we haven't implemented yet is to update the wiki when new emails arrive. That is the next one in our backlog.
For coding agents, the biggest improvement for me wasn't a different editor, it was making the tool/context path inspectable. If a skill or memory block gets injected, I want to see exactly why it was selected and what text it added. Otherwise the agent can look “smart” for one run and be impossible to debug the next time it takes a weird detour.
yes, continue it.
I archived my agent, but now revived it, keep building it, not just for selling it, the building itself is the real fun, learn a lot, build while changing direction, will be something someday.
It can be, however it's not fully deterministic, because the agent can hallucinate or misbehave, which is fairly common. Because MCP is a separate process, we can ensure that safety pipeline is fully followed.
Linggen is an agent with a WebUI and P2P architecture, which sets it apart from tools like Claude Code and OpenClaw. The name is inspired by the Chinese fantasy novel Fanren Xiuxian Zhuan. It started as a fan project but is designed for practical daily use.
Built in Rust, it is fast to install (seconds) and remains lightweight under heavy workloads, including multiple sessions, extensive tool usage, and sub-agent execution.
Author here. Built this because I wanted one system where I could drop a markdown file and get a new agent
— for coding, but also for scheduled code reviews, architecture checks, or anything else.
The file-based approach is the core idea. An agent is 15 lines of YAML + markdown. A skill is a SKILL.md
directory. A mission is a cron entry pointing at an agent. No SDKs, no plugins, no code changes — just
files.
Happy to go deep on the Rust runtime, multi-agent delegation, or anything else.
reply