amal66 ↗ analysis ↗ GitHub amal66/mike
Mike moved into Microsoft Word, made self-hostable and pluggable, and hardened for production legal work.
The centerpiece is a Microsoft Word add-in. amal66 has built Mike into a task pane that sits inside the document a lawyer already has open: a chat assistant that can see what you're drafting, one-click document actions, and tabs for workflows and projects. No copying text out to a browser and pasting answers back. The add-in landed as a six-layer series of reviewable pieces, which tells you something about how this fork is run.
Around that, the fork is being reshaped into something you can operate yourself. There's a one-command Docker setup for running the full stack on your own servers, swappable registries for AI providers and file storage, a plugin system for wiring in jurisdiction-specific legal sources, a Python SDK, and workflows that export to shareable files.
The third thread is a long security and reliability pass: defenses against documents that smuggle instructions to the AI, uploads vetted by actual file content, message quotas enforced server-side, and logs scrubbed of user and document identifiers. Nothing identifies amal66 beyond the handle, but the fork also picked up CI, a test suite, and contributor docs - the work reads like preparation for real deployments and outside contributors.
What's in it
- Microsoft Word add-in A task pane inside Word with Mike's chat, one-click document actions, and workflow and project tabs. The chat can read the document you have open.
- Self-hosted deployment One command stands up the full web-and-API stack locally with Docker Compose, for anyone who wants Mike on their own servers.
- Bring your own AI engine Swappable AI providers and file storage. Changing either is a small, contained job instead of surgery on the core.
- Jurisdiction plugins A law-library plugin system for bolting local legal sources onto Mike without rewiring the rest of the app.
- Python SDK A ready-made client for engineers who want to build on Mike's API without dealing with the plumbing.
- Security hardening Prompt-injection defenses for untrusted documents, uploads checked by real content rather than filename, server-enforced usage quotas, and an access fix that stopped users from reading each other's data.
- Portable workflows Reusable legal workflows export to shareable files that move between Mike installations.
Direction
integrationsecurityinfrastructure
Activity
amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub Show 15 more
Threads of work (detailed view)
amal66 turns Mike into a bring-your-own-engine platform
The fork rebuilds how Mike connects to AI models and file storage so swapping either one becomes a small, contained job instead of open-heart surgery.
amal66 hands Python developers a front door into Mike
A ready-made toolkit lets engineers plug into Mike's features without wrestling with the plumbing underneath.
amal66 turns Mike into a kit for jurisdiction-specific legal AI
A new plugin system lets you bolt local legal sources onto Mike without rewiring the core.
amal66 closes the books by hardening the plumbing - and admitting what it can't
The final stretch of amal66's fork tightens reliability and self-hosting while openly parking the credential-heavy work for later.
amal66 puts Mike's riskiest parts under test
This fork is treating an automated test suite as a shippable feature, not an afterthought.
amal66 puts a fence around documents the AI can't trust
A defense against documents that try to hijack the AI by smuggling instructions into their own text.
amal66 puts a real lock on the meter
Per-user message limits now get enforced on the server before any expensive AI call fires - not just shown in the interface.
amal66 lets legal workflows pack up and travel
A fork owner is turning reusable legal know-how into shareable files that move between Mike setups without touching a database.
amal66 puts the database under lock and key
Three changes that make amal66's fork harder to misuse and harder to corrupt - work borrowed straight from the upstream project.
amal66 is teaching Mike's AI calls to fail gracefully
Two changes stop a flaky AI provider from freezing the app or surfacing errors that didn't need to surface.
amal66 makes Mike something you can run on your own servers
A new one-command setup lets anyone stand up Mike's full web-and-API stack locally instead of wiring it together by hand.
amal66 stops its legal logs from remembering who touched what
A cleanup pass pulls user and document identifiers out of this fork's logs and treats activity records as sensitive data, not debugging exhaust.
amal66 makes Mike check what files actually are, not what they claim to be
Uploaded documents now get vetted by their real content, so a renamed or mislabelled file can't sneak past as something it isn't.
amal66 hardens how Mike guards stored keys and download links
A trio of security fixes pulled from upstream that make secret handling sturdier without breaking anything already in place.
amal66 puts guardrails on how much Mike will swallow and serve
A reliability pass that caps oversized requests, paginates long chat histories, and makes crashes leave a trail.
amal66 puts a ceiling on what the app will swallow
A round of plumbing work caps how much a single request can demand and keeps the system standing when something goes wrong.
amal66 closes a door that let users read each other's data
A fork tightens who can open structured documents - and fixes a bug that several Mike forks all hit independently.
amal66 is getting Mike ready for real deployment
A quiet but practical round of hardening aimed at running Mike in production rather than on a laptop.
amal66 is building an AI chat assistant into Microsoft Word
A drafting copilot that lives inside the document, not in a separate tab you paste into.
amal66 builds out the Word add-in with Workflows and Projects
The final layer of a six-part effort to make Mike work where lawyers already do - inside Microsoft Word.
amal66 wires one-click actions straight into Word
The fork's Microsoft Word add-in gains an Actions tab, so common document tasks run without leaving the editor or opening a chat.
amal66 is putting Mike inside Microsoft Word
A staged effort to let lawyers call the legal-AI assistant without leaving the document they're drafting.
amal66 is teaching Mike to live inside Microsoft Word
The first, invisible layer of a Word add-in: the backend handshake that lets Mike see the document you have open.
amal66 puts Mike inside Microsoft Word
A task pane add-in that drops Mike's chat, actions, and workflows straight into the document a lawyer already has open - no copy-out, paste-back.
Pull requests (detailed view)
⛔ Closed without merge (7)
amal66 · opened 24d ago · closed 23d ago amal66 · opened 24d ago · closed 23d ago amal66 · opened 24d ago · closed 23d ago amal66 · opened 24d ago · closed 23d ago amal66 · opened 24d ago · closed 23d ago amal66 · opened 24d ago · closed 23d ago amal66 · opened 25d ago · closed 23d ago