A myNeutron Alternative for Keeping Track of Work, Not Just Reading

Whether you need a myNeutron alternative comes down to one question: are you trying to remember what you have read, or what you and your team are doing? myNeutron is a browser-based “second brain” that captures web pages, email, documents and chats and lets you find them again by meaning, then hand them to an AI app. For research and reading it is a sensible choice. For keeping track of tasks, decisions and where the work stopped, so that other people and other AI apps can pick it up, a shared board such as fenbs does that job. They solve different problems and work well together.

What myNeutron does

myNeutron is a Chrome extension. Its Chrome Web Store listing↗ (opens in a new tab) describes it as a way to “Save and recall any chat, note, or file as you browse.” According to that listing:

• It sits in your browser and captures the pages, emails, documents and chats you choose to keep.
• It stores them by meaning rather than exact words, so you can search for “that report about renewable energy I read last month” and find it.
• You can connect Gmail and Google Drive, so your email and files become searchable in the same place.
• You can send what you captured into ChatGPT, Claude, Gemini and other AI apps to summarize, translate or build on it, instead of copying and pasting.

The same listing says future updates will include mobile sync and “secure sharing options so you can collaborate with your team or family.” As described today, then, it is a personal tool. Check myNeutron’s own site for anything newer before you decide.

Who should keep myNeutron

• Researchers, students and analysts who read a lot online and lose track of where they saw something.
• People whose most useful material is buried in their inbox and their drive, and who want to ask an AI about it without hunting for each file.
• Anyone who wants a personal knowledge base that several AI chat apps can draw on.

If that is you, the closest alternatives are other personal memory tools rather than a work board. MemoryPlugin centers on memories about you and your imported chat history; AI Context Flow organizes saved briefs and files into project spaces and adds an MCP server; MemoryLake stores typed, versioned memories and many file types. The portable AI memory roundup compares all four.

What a reading memory does not cover

A second brain is a library. It is very good at “where did I read that?” It is not built to answer the questions that come up when work moves between people, or between AI apps:

• What is still to do, what is in progress, and what is finished?
• What did we decide, and who decided it?
• Which rules must every AI assistant follow on this project?
• Where exactly did I, or the assistant, stop yesterday, and is anything still waiting on a person?
• Who changed this, and when?

An example makes the gap clear. Say you research suppliers for a month and save every page and email in your second brain. Then you hand the project to a colleague, who works in Claude while you use ChatGPT. Your second brain helps you remember what you read, but your colleague cannot see it, and nothing in it says which suppliers you ruled out, why, or what the next step was. They start again, and so does their assistant.

Those answers need a record that people write and own, and that every AI app reads the same way. That is closer to a task board than to a memory. Our explainer on what agent memory is covers where the line falls.

The built-in option: your AI app’s own memory

Before adding any tool, check what your AI app already does. Claude and Gemini can both take in a summary of what another assistant knows about you. Google’s help page on importing into Gemini↗ (opens in a new tab) describes a prompt you paste into your old chatbot and a way to upload exported chats, and Anthropic’s help center describes a similar memory import for Claude↗ (opens in a new tab). These are one-time moves, not a live sync: once imported, the memory lives with that vendor. See Claude import memory for what moves and what does not.

How fenbs keeps track of the work

fenbs is a web app: a simple kanban board where people and every AI app they use keep projects, tasks, decisions and rules, lessons learned and where they left off. AI apps such as ChatGPT, Claude, Claude Code, Codex and Cursor connect to it over MCP, the standard way an AI app plugs into an outside tool (explained here). Because they all read the same board, you can switch app or model without starting over.

• Tasks: features, enhancements and bugs in four lanes, To Do, Next Up, In Progress and Completed.
• Decisions and rules: written by people, shown to every assistant first. Assistants can ask but never decide, and cannot sign off a decision or pre-approve work.
• Where we left off: saved per project when you tell your assistant “save progress,” with Where it stands on each task it touched.
• History: every change, with the person or the named assistant who made it.
• Team boards: you add colleagues with a role, so they see and change only what that role allows.

fenbs does not capture web pages, read your email or search your drive. If you need that, keep myNeutron or a similar tool for your reading, and use the board for what you are doing about it.

Three checks before you switch

• What it captures. A tool that watches your browsing, email and drive sees a lot. Decide which sites and accounts it should see, and read the privacy policy linked from the listing before you connect Gmail or Google Drive.
• Who needs to see it. If the answer is only you, a personal tool is fine. If a colleague or a contractor needs the same picture next week, choose something built for sharing with roles now, rather than waiting for a sharing feature to arrive.
• Which AI apps you use. Make sure every assistant you rely on is covered, including desktop and coding apps, not only the chat websites in Chrome.

If the honest answer to the second check is “my team,” keep your reading where it is and put the work on a board everyone can open. Your second brain stays yours, and the board becomes the place where the team, and every assistant it uses, finds out what is happening.

A simple way to split the two

1. Reading, research and reference material: your second brain.
2. Anything somebody has to act on: a task on the board, with a note saying why and where.
3. Anything somebody decided: a decision on the Decisions and rules page, so every assistant follows it.
4. The end of each session: “save progress,” so the next one, in any app, starts in the right place.