Differences from M.A.V.E.N
| Count | ||
|---|---|---|
| Carried over whole | 18 | Every control, every tab, every picker. |
| Folded into another app | 4 | Behaviour survives; the sidebar entry does not. |
| Left in M.A.V.E.N | 4 | This product is about what a team shares. |
| New in Teams | 7 | Everything built on the event log. |
A unit test (carryOver) holds that list next to an assertion: a route promised to
carry over that does not exist fails the suite.
Carried over whole
Section titled “Carried over whole”Ad-Forge, AI Mastermind, D-Forge, G-Forge, Health, M-Forge, Media Library, Memory, N-Forge, P-Forge, R-Forge, S-Forge, SEO-Forge, Telemetry, Thumbnails, VC-Forge, X-Forge - and the top-bar chrome: the Model Manager that every picker reads, alerts, help, health, secrets, the command palette, the running-tasks badge, the update banner and the language switch. Where the Teams design showed fewer controls than M.A.V.E.N had, M.A.V.E.N won.
Folded into another app
Section titled “Folded into another app”- Loop, Pipeline and Kanban → Workflows. One shape: an ordered list of steps, some of which wait for a person. Existing state is not converted; recreate the ones you still want.
- Hermes Swarm → a tab inside Hermes. A swarm is Hermes running many at once; as a
separate rail entry it looked like an unrelated product. The agent roster moved the
same way, from
/agents/…into an Agents tab.
Left in M.A.V.E.N
Section titled “Left in M.A.V.E.N”Game Studio, Music, Open Design, OpenMontage, Paperclip. The first four are personal creative tools; nothing about them gets better when a second person can see the screen. Paperclip is an embedded tracker on another port, and Teams grew its own patch queue - Git & Review - where a merge is a decision on the log; two trackers side by side is exactly the split-brain this product exists to remove.
New in Teams
Section titled “New in Teams”Chat (the merged consoles, as in M.A.V.E.N ≥ 6.14 - minus OmniRoute, which routes to engines and would make “which model am I talking to” ambiguous), Channels, Workflows, Search, Audit log, Local / Cloud, Hermes as its own rail entry, Git & Review, and a Settings that holds Relay, keys and models in one place.
The rail was rebuilt, not renamed
Section titled “The rail was rebuilt, not renamed”M.A.V.E.N’s sidebar has six sections and lists every agent and every model as a destination. Teams has four groups - WORKSPACE, BUILD, FORGE, SYSTEM - and no vendors in any of them. The models moved into the Model Manager; the agents moved inside Hermes.
State: nothing is shared
Section titled “State: nothing is shared”Teams keeps its state in ~/.maven-teams, not ~/.maven - the two share seventeen
filenames, settings.json among them. Bring your keys across by copying .env.local;
nothing else carries over, and nothing in M.A.V.E.N is touched by installing Teams next
to it. Both can run on one machine: M.A.V.E.N on :3000, Teams on :3400.