Features
The feature surface is bigger than review.
Mike OSS lineage · feature map · availability depends on the evaluation build
The point of the Mike lineage is not to bolt an agent onto a document viewer. It is to give legal work a connected surface: source material, repeatable instructions, structured review and a human decision in one traceable loop.
This page documents the public feature surface of the Mike OSS lineage that Vaultr is based on. Cards marked Public Vaultr surface are already documented in the current Vaultr site. The remaining cards describe upstream capabilities being carried into the fork; availability, platform support and mode boundaries must be confirmed in the specific evaluation build rather than inferred from a marketing page.
The matter room
Start with the documents already on the table. The workspace keeps a matter's context together so the assistant can work from the bundle, not from a blank chat window.
Chat with legal documents
Ask questions of a document or an open matter in plain language, with the relevant passage kept in view.
Public Vaultr surfaceProjects, folders and matters
Organise work into projects, folders and a document library instead of treating every upload as a disposable prompt.
Document library
Keep the source set discoverable and reusable across the matter. The library is the beginning of context, not an afterthought.
Grounded citations
Answers and findings point back to the material they rely on. A source is part of the result, not a footnote added later.
Public Vaultr surfaceReview at scale
Move from one clause to a portfolio of documents without losing the reviewer's line of sight. Review outputs remain structured, inspectable and tied to the source.
Document review
Review agreements against a playbook, surface issues and apply suggested edits while keeping the human decision in the loop.
Public Vaultr surfaceTabular review
Extract structured answers across many documents into a spreadsheet-style table. Columns describe the questions; cells remain traceable to page and quote.
Review-result interrogation
Chat with the results after a tabular run. Ask follow-up questions about the extracted set instead of starting the analysis again.
Suggested edits with approval
The system proposes; counsel accepts, edits or rejects. Review is not complete merely because a model produced a redline.
Public Vaultr surfaceResearch and drafting
The feature surface extends beyond document Q&A: research, precedent and drafting belong in the same working context when their sources stay visible.
Legal research
Research US case law through CourtListener, with the research path separated from unsupported general answers.
Precedent-grounded drafting
Draft letters, clauses and summaries from the matter and the precedent set you provide, rather than from an invisible generic corpus.
Public Vaultr surfaceDraft and edit in context
Review a proposed change, continue the conversation and keep the source material beside the work product instead of switching tools for every step.
Interactive requests
A workflow can ask for missing facts, a template or an additional document before continuing — the assistant does not have to guess what is absent.
Agents, skills and workflows
The differentiator is not just a larger chat box. Reusable instructions turn good legal work into an inspectable practice that can be shared, improved and run again.
Agent-assisted work
Use an assistant that can move through multi-step legal tasks, request inputs and return a structured result rather than one opaque paragraph.
Reusable assistant workflows
Package repeatable instructions for drafting, review and research so a workflow can be run consistently across matters.
Tabular-review workflows
Define the questions and columns for a bulk review separately from the presentation layer, then render the result as an interactive table.
Shareable workflow repository
Inspect, adapt and contribute workflow definitions. System workflows and add-on packs make the library extensible instead of locked to one vendor's prompt menu.
Connect the work to your tools
A legal workspace has to meet people where they already draft, search and communicate. These are explicit connections — not hidden data paths.
Microsoft Word task pane
A beta Word add-in brings the assistant into the document window where drafting and review already happen.
MCP connectors
Connect remote MCP servers from settings, using the provider's consent flow or credentials you configure for the deployment.
Slack connection
Search and work with the Slack context an authorised user can access, with connector-level controls rather than a blanket import.
Local models through Ollama
Run supported language models locally through Ollama when the deployment and model fit call for it.
Self-hostable deployment
Run the stack with local infrastructure and keep ownership of the application, storage and model configuration under an AGPL-3.0 licence.
What Vaultr changes about the surface
Same breadth, different default
The Mike feature surface is broad. Vaultr's default remains local-first: external model paths are named, visible and explicit.
Every feature has a boundary
Research, connectors, Word and agents are not exceptions to the trust model. Each must say what leaves the device and when.
The human still closes the loop
A workflow can do more steps; it does not get to make the final legal decision. Review, edit and approval stay with counsel.
Open workflows stay open
Instructions should be inspectable, portable and improvable — not hidden behind an uneditable prompt catalogue.
See the parts that are public today
Start with the surfaces you can inspect now, then request an assisted evaluation for the workflow and integration features you need to test against a real bundle.
Feature research checked against the public Mike homepage, the Open-Legal-Products/mike repository and the public workflow repository. Upstream references are linked for inspection.
Mike OSS reference