MENO / CHANGELOG
Watch Meno
take shape.
We are building the shared workspace one useful release at a time. Here is what we have been making, and the reason each piece matters.
This is a development log through September 28, 2026. Features described here are built on our product branch; some remain in private development or testing and are not yet available to every early access team.
SEPTEMBER 14–17, 2026
A shared place takes shape.
We started with the everyday work: finding what matters, knowing who did what, and giving people and agents the same grounded record to work from.
The right context becomes findable.
We added readable company context documents, workspace search, code search, and an MCP tool surface for external agents. The first step toward better context selection is a record that can actually be found and checked.
- Search work and custom fields from the workspace.
- Bring authorized Meno context into an external agent session.
Agent work should have a name on it.
An external agent can use Meno tools through the signed-in person’s access to search permitted context and contribute to the record. We made its comments and revisions show both the person and the agent behind the change.
- Search with the same access boundaries as the person authorizing the agent.
- See agent attribution where comments and revisions appear.
The day gets a clearer home.
We built a new workspace view for home, tasks, board, inbox, projects, documents, chat, team, search, and mobile navigation. Checklists, subtasks, tags, profiles, and notifications make the small pieces of work easier to see and finish.
- Move from a project to its tasks, discussions, and documents.
- See who is on the team and what needs your attention.
SEPTEMBER 19–24, 2026
The workspace reaches beyond itself.
The work does not end at a task card. It reaches code, conversations, and the people who need to make the call.
A task can follow its change into code.
We connected selected GitHub repositories to a workspace. A task can show its branch, changed code, and pull request. An agent can prepare a branch and open a review through the signed-in person’s access; a person remains the one who merges.
- Choose which repositories a workspace can see.
- Review the code linked to a task without losing the task’s purpose.
A conversation can travel with the work it explains.
We built citation paths for Slack and Microsoft Teams messages, so a useful quote can sit beside a task or decision with a route back to its source. The connector flows are still being tested before they are generally available.
- Attach a cited message to the work it helps explain.
- Keep the source visible instead of turning a conversation into anonymous context.
A place for an actual team to arrive.
We added account and workspace creation, invitations, password recovery, notification delivery, and a path to close an account. These are quiet features, but they make the workspace something a team can enter and manage on its own.
- Invite people into the workspace and make failed invitations visible.
- Receive the digests and notifications the workspace prepares.
Take a copy of your own data.
We added a download for the account and work a person can take with them. It includes what they wrote, filters surrounding workspace details through their current access, and leaves connected account credentials out.
- Download a readable JSON copy from account settings.
- Keep your own record without asking us to prepare it.
SEPTEMBER 26–28, 2026
The work starts to explain itself.
A company makes thousands of small choices. We are making the reasons easier to find, follow, and carry into the next piece of work.
History you can return to.
Tasks, documents, and projects gained a readable change history. When the body of a document needs to go back, a person can restore a previous version without pretending the rest of the workspace went back with it.
- See what changed, who changed it, and the reason recorded with it.
- Put acceptance criteria directly on a task before the work begins.
Ask why the work looks the way it does.
We brought the decision record into the browser and built a way to ask why a file is the way it is. The answer can point to the recorded work behind it, while quoted messages from chat become findable too.
- Read decision records and start a proposed decision from the workspace.
- Find quoted chat context and follow it back to its source.
Decisions now have a trail in both directions.
A decision should show what came before it and what it changed. We built links between decisions, tasks, files, and reviews, including a visible path when one decision replaces another.
- Follow a decision to the work connected to it, and back again.
- See when a newer decision supersedes an older one without erasing the history.
WHAT COMES NEXT
The record keeps growing.
Our next push is making Meno better at choosing the right context for each person and agent, across the work a company already does. We will keep showing the work as it becomes real.
Get early access →