amal66 ↗ analysis ↗ GitHub amal66/mike
A security-minded, self-hosted legal AI platform expanding into firm workspaces, everyday tools, and Microsoft Word.
amal66 is shaping Mike into a fuller legal-work platform for teams that want more control over where it runs, which AI services it uses, and who can access shared work. The fork has a clear self-hosting story, with stronger operational safeguards around documents, credentials, downloads and connected services.
The product direction is practical and ambitious: firm workspaces with role-aware access, connected knowledge from services such as Google Drive and Slack, and a Microsoft Word experience that brings chat, workflows and document actions into the drafting environment. It also puts unusual emphasis on making AI answers, citations and security controls more trustworthy.
This is an active fork with enough breadth to reward a closer look on GitHub, particularly for legal teams considering a controlled deployment rather than a standalone chat tool.
What's in it
- Self-hosted legal AI A full-platform deployment option for teams that want to run Mike on their own infrastructure.
- Firm workspaces and permissions Organisation-level workspaces and role-aware access controls support shared legal work without losing individual workflows.
- Microsoft Word workspace A Word add-in brings chat, workflows, projects and one-click document actions into the editor lawyers already use.
- Connected knowledge sources Planned and delivered connector work points toward controlled access to sources such as Google Drive and Slack.
- Safer AI and document handling The fork invests heavily in citation checking, prompt-injection boundaries, expiring downloads, upload validation and tighter access controls.
- Reliability and release discipline Broader testing, quality gates and deployment safeguards aim to make legal-work changes easier to trust.
Direction
securityintegrationmulti-tenant
Activity
amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub Show 147 more
amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub amal66 ↗ analysis ↗ GitHub Threads of work (detailed view)
amal66 makes Mike's database upgrades prove they match fresh installs
A new safeguard catches the quiet database drift that can leave upgraded and newly installed Mike systems behaving differently.
amal66 brings Mike's assistant into Microsoft Word
This fork turns Word into a practical front end for Mike, while leaving lawyers in control of each edit.
amal66 makes Mike's accessibility checks pull their weight
This fork turns accessibility from a late-stage concern into a routine quality check, while fixing barriers it already found.
amal66 makes Mike's privacy checks harder to wave through
A new review gate now tests whether a fresh Mike installation actually keeps browser access locked down.
amal66 makes chat reliability a deliberate test discipline
This fork adds deeper checks for the security controls and chat streams that can fail quietly in ordinary testing.
amal66 makes chat quotes earn their citations
This fork stops a polished AI answer from passing off invented document language as a real quote.
amal66 puts a guardrail around hostile documents in Mike's chat
The fork makes it harder for a malicious file to masquerade as instructions when staff use AI-assisted legal workspaces.
amal66 gives Mike's chat a stronger prompt-injection boundary
The fork adds a practical safeguard against malicious instructions hiding inside legal documents and project material.
amal66 puts Mike's frontend quality gate back to work
A broken test check had made every new contribution look suspect, even when the tests themselves passed.
amal66 closes a dangerous back door in bring-your-own connectors
The fork makes it far harder for a normal account to turn a connector into a probe of the platform's private systems.
amal66 gives Mike's security posture a proper front door
The fork makes it easier to report problems privately and harder for security mistakes to slip into the project unnoticed.
amal66 makes Mike a self-hosted proposition
This fork packages the platform for organisations that want more control over where legal work and data run.
amal66 puts Mike's full platform in a self-hosted box
A previously stalled self-hosting effort is back, making Mike more practical for teams that want to run the whole platform on their own infrastructure.
amal66 makes AI testing a maintainer decision
This fork turns a fragile-looking AI test suite into an explicit, auditable release check.
amal66 makes Mike prove its core journeys before shipping
This fork adds a real browser check that can catch broken legal-workflow basics before a pull request lands.
amal66 locks Mike's browser access to known doors
A tighter web-access policy reduces the chance that a hostile website can read data from an authenticated Mike session.
amal66 gives Mike's client-side chat a safety net
A new testing gate aims to catch broken conversations, uploads and sign-in flows before they reach users.
amal66 puts legal-document handling through its paces
A new testing layer is designed to make the platform less likely to mishandle the documents, citations and workflows lawyers rely on.
amal66 puts Mike's access controls under pressure
This fork adds direct testing of the boundaries that should keep one client's legal material out of another's hands.
amal66 puts Mike's API access controls under a microscope
A new test suite is designed to catch the kinds of access failures that matter most when legal documents sit behind an API.
amal66 stops silent dependency corruption at the gate
A small safeguard makes Mike's build process much less likely to hide a broken dependency merge behind a misleading installation error.
amal66 stops project pickers from hammering the platform
Opening a project picker now makes one coordinated request instead of triggering a burst of lookups for every project.
amal66 puts guardrails around Mike's riskiest backend work
This fork invests in the unglamorous checks that keep legal workspaces, documents and credentials from failing in expensive ways.
amal66 turns frontend quality checks into a real gate
A clean slate means new frontend mistakes now stop at review instead of becoming the next inherited backlog.
amal66 puts guardrails under Mike's web refresh
The fork adds a safety net for the shared interface pieces that users encounter most often.
amal66 puts a safety net under Mike's access controls
A new test suite targets the backend rules that decide which projects and documents a user can see.
amal66 makes testing expectations visible
A contributor-facing testing guide and pull-request checklist make verification an explicit part of changing Mike.
amal66 makes proof part of the proposal
This fork turns testing from an implied expectation into a visible part of contributing.
amal66 puts a fast quality gate in front of changes
A new automated check aims to catch broken releases before they reach the main line of development.
amal66 adds a real pre-merge safety net
This fork now checks that both sides of the product can still build before a pull request lands.
amal66 gives Mike a testing safety net
A small change makes future improvements easier to trust before they reach legal teams.
amal66 puts Gemini behind Google Cloud's guardrails
This fork makes Mike easier to run inside organisations already governed through Google Cloud.
amal66 brings Gemini under enterprise controls
This fork makes Google's Gemini models a more realistic option for tightly governed legal AI deployments.
amal66 gives Mike a Python front door
The fork adds a Python toolkit so legal-automation teams can connect their own systems to Mike more directly.
amal66 gives Mike a plug-in path into Danish law
The fork adds a structured way to connect jurisdiction-specific legal sources to the chat experience.
amal66 opens Mike to local and future AI engines
This is a foundational change that makes Mike less tied to a fixed set of AI providers and storage choices.
amal66 is making Mike's AI connections easier to extend
The closed proposal would replace a tangle of provider-specific handling with a single, reusable way to add AI services.
amal66 turns hardening follow-ups into a sturdier Mike
This fork converts a backlog of reliability concerns into tested safeguards across the product's most failure-prone edges.
amal66 makes AI outages less likely to derail legal work
The fork adds a second chance when an AI provider fails temporarily, with checks around switching models when needed.
amal66 puts a meter on AI chat usage
This fork makes monthly message limits a hard gate before an AI chat request is sent.
amal66 makes legal workflow packs portable
Teams can now move reusable legal workflows between Mike environments, with clearer rules for what a valid pack contains.
amal66 lays the groundwork for safer database upgrades
The fork begins turning its database setup into a managed upgrade history, a meaningful step for teams running the product beyond a one-off local install.
amal66 makes Mike's audit trail less likely to spill client data
This fork replaces ad hoc chat logging with structured records that make individual requests easier to trace.
amal66 gives uploads a reality check
This fork stops trusting a file's name and starts checking whether its contents match the claimed format.
amal66 hardens the lockbox for AI provider keys
A focused security upgrade makes stored credentials less vulnerable to reuse if one record is exposed.
amal66 puts a supply-chain gate in front of Mike
This fork turns dependency security from a periodic clean-up into a visible, reviewable release condition.
amal66 puts an alarm on Mike's software supply chain
This fork turns dependency security from an occasional clean-up into a release-blocking control.
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 small but real sharing-access gap
A narrow access-control fix makes invited collaborators less likely to be locked out because their email address is written differently.
amal66 locks public legal-data tables by default
A new security baseline denies access to public-facing data unless an explicit policy permits it.
amal66 puts an expiry date on sensitive downloads
New document links now time out, reducing the risk that a forwarded or leaked URL becomes a permanent route to confidential material.
amal66 wants confidential download links to expire
The proposal would limit how long a leaked document link can remain useful, without immediately breaking older links in chat histories.
amal66 puts a timeout on stuck AI answers
A small reliability guard stops a stalled AI connection from leaving a legal-workflow chat hanging indefinitely.
amal66 turns Mike's backend into guarded domain modules
The fork reorganises a sprawling backend without changing what its 222 existing endpoints do.
amal66 gives Mike's backend a clearer legal-work spine
A behind-the-scenes restructure aims to make future changes safer without changing how Mike behaves today.
amal66 is rebuilding Mike around a shared workspace
This is not a new legal-AI feature, but it makes a heavily modified fork more practical to evolve.
amal66 is hardening Mike for the loading dock
The fork adds the basics that make an application safer and easier to operate once it leaves a developer's machine.
amal66 makes Mike refuse unsafe deployments
The fork now stops at startup when its essential operating settings are missing, rather than failing later on a sensitive request.
amal66 tries to stop database drift before it reaches main
A small consistency fix targets a failure that can leave fresh installations and upgraded systems structurally out of step.
amal66 makes chat titles stop crashing short conversations
A small reliability fix removes a hidden failure point in fast-finishing chat sessions while making the product's checks far more dependable.
amal66 makes the Word add-in prove it matches the product
A small design fix becomes a useful guardrail against a Word workspace quietly drifting from the main application.
amal66 turns paper-thin safety checks into real gates
This fork replaces reassuring green ticks with checks that actually protect the legal-AI system, and removes the ones that cannot.
amal66 is making citation badges earn their authority
A citation check should catch a misleading abbreviation, not certify it.
amal66 turns chat excerpts into parallel side investigations
A new workflow would let lawyers probe or revise one passage without losing the thread of the wider conversation.
amal66 makes chat answers quotable context
A small interaction change could make follow-up questions much more precise without turning chat into a copy-and-paste exercise.
amal66 puts a traffic cop on bulk document uploads
Large document batches should now fail more gracefully, without losing the files that made it through.
amal66 wants durable work queues without adding Redis
The unmerged proposal would make failure-prone background work survive restarts using the Postgres database most Mike deployments already have.
amal66 brings chats into the permissions fold
This makes shared legal work easier to find and harder to access by mistake.
amal66 is giving Mike's legal workflow plumbing a safety overhaul
This proposed follow-up targets the unglamorous failures that can make a legal AI tool feel unreliable or unsafe in daily use.
amal66 puts the whole Mike stack on a Mac
A new local mode aims to let one person run Mike privately, without Docker, a hosted server or an account.
amal66 gives self-hosted Mike a controlled connectors layer
Firms can link Mike to the information sources their people already use, without giving the platform broader access than each user holds.
amal66 gives Mike a proper Mac front door
A lightweight Mac app makes Mike feel desktop-native without splitting the product into two versions.
amal66 moves Mike's heavy lifting off the front desk
A proposed job system shifts slow and failure-prone work out of the live user request, without forcing every installation to add new infrastructure.
amal66 brings Slack workspace context to Mike, with the brakes on
The proposal would let Mike draw on Slack conversations and knowledge while keeping write actions disabled by default.
amal66 brings Google Drive into Mike's chat, but the connector stays on the shelf
The proposal would have turned a connected Drive into a searchable, readable source for legal work inside Mike.
amal66 makes Google's connector setup less fragile
This closed proposal aimed to turn a brittle Google connection flow into one that tells organisations exactly what they need before it breaks.
amal66 gives firm workspaces a real chain of command
The fork turns organization ownership and project roles into visible, usable controls rather than back-end plumbing.
amal66 makes Mike fit a law firm, not just a lawyer
This fork adds firm-level workspaces and clearer permissions without disrupting lawyers who use Mike on their own.
amal66 brings local AI into the Mike stack
A closed proposal would let self-hosted teams keep both their legal documents and AI inference on their own hardware.
amal66 makes Mike usable before the API keys arrive
A proposed demo mode would let a fresh Mike installation answer its first question offline instead of greeting users with an authorization error.
amal66 tries to put Mike's safety checks on a hard fail
The proposal would have made it much harder for a seemingly harmless change to quietly weaken safeguards around legal AI responses.
amal66 tries to make security checks worth listening to
The fork proposed a review-time security screen designed to catch real hazards without drowning reviewers in false alarms.
amal66 makes legal AI connectors ask first
This fork changes the default from trusting connector labels to requiring a person to approve anything not clearly safe.
amal66 puts connector credentials behind a stronger lock
The proposal would protect the passwords and tokens that let Mike connect to services such as Gmail, Slack and GitHub.
amal66 tries to make legal AI safety testable before it ships
A proposed offline scorecard would let teams catch unsafe legal-AI behaviour without paying for live model runs.
amal66 proposes a serious server-security upgrade for Mike
A closed, unmerged proposal would add practical safeguards around connected tools, confidential files and AI-generated legal answers.
amal66 puts an expiry date on document download links
The fork proposes closing a quiet but important document-access loophole: download links that could otherwise work forever.
amal66 puts a lock on Mike's chat intake
The proposal would stop hostile text hidden in legal files from masquerading as instructions to an assistant with access to sensitive matter material.
amal66 wants document citations to earn their authority
A closed proposal tackles a legal AI risk that matters more than a polished answer: a quote attributed to a document that is not actually there.
amal66 tries to lock down Mike's connector back door
The proposed change would stop user-supplied AI connectors from turning Mike's server into a route into its own private network.
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)
🟢 Open (14)
amal66 · opened 2mo ago #295 [Architecture] refactor: per-domain modules with service layers, enforced by an architecture test - pure motion, zero new deps amal66 · opened 3mo ago #356 [Quality] Repo-wide audit fixes: error containment, drifted forks, silent failures (stacked on #294→#295) amal66 · opened 2mo ago amal66 · opened 3mo ago amal66 · opened 2mo ago amal66 · opened 2mo ago amal66 · opened 2mo ago amal66 · opened 2mo ago amal66 · opened 2mo ago amal66 · opened 2mo ago Show 4 more open
#405 fix: chat-route tests off the network, and a write-after-end crash the flake was hiding amal66 · opened 2mo ago #351 [Mac app] Self-contained local mode - the whole stack runs inside Mike.app (stacked on #302) amal66 · opened 2mo ago amal66 · opened 3mo ago #381 fix: bound client upload concurrency and surface per-file outcomes (issue #8 follow-up to #294) amal66 · opened 2mo ago ✅ Merged (31)
#363 [Orgs] 3 Chat permission parity: chats join the project role ladder (stacked on #268) amal66 · opened 2mo ago · merged 2mo ago by willchen96 #268 [Orgs] 2 Organization management UI + role-aware permission gating (stacked on #267) amal66 · opened 3mo ago · merged 2mo ago by willchen96 amal66 · opened 3mo ago · merged 2mo ago by willchen96 #294 [Architecture] feat: durable job queues - BullMQ-primary with Postgres fallback, worker threads, async-on for new installs amal66 · opened 3mo ago · merged 2mo ago by willchen96 amal66 · opened 2mo ago · merged 2mo ago by willchen96 #293 [Testing 17] ci: schema-drift check - fresh install vs upgraded deployment must converge amal66 · opened 3mo ago · merged 2mo ago by amal66 amal66 · opened 3mo ago · merged 2mo ago by willchen96 #221 [Feature 14] feat: Word add-in - chat, tracked-changes rewrites, workflows and projects in Word amal66 · opened 3mo ago · merged 3mo ago by willchen96 amal66 · opened 3mo ago · merged 3mo ago by willchen96 amal66 · opened 3mo ago · merged 3mo ago by willchen96 Show 21 more merged
amal66 · opened 3mo ago · merged 3mo ago by willchen96 #282 Self-hosted Docker stack (embedded Supabase + storage + email) and local Ollama models (supersedes #196) amal66 · opened 3mo ago · merged 3mo ago by willchen96 amal66 · opened 3mo ago · merged 3mo ago by willchen96 #281 test(frontend): fix the red main - pay down the coverage regression from #274/#263/#280 amal66 · opened 3mo ago · merged 3mo ago by willchen96 amal66 · opened 3mo ago · merged 3mo ago by willchen96 amal66 · opened 3mo ago · merged 3mo ago by willchen96 amal66 · opened 3mo ago · merged 3mo ago by willchen96 amal66 · opened 3mo ago · merged 3mo ago by willchen96 amal66 · opened 3mo ago · merged 3mo ago by willchen96 amal66 · opened 3mo ago · merged 3mo ago by willchen96 #220 [Testing 12] test: Playwright e2e suite + CI merge gate (auth, chat, projects, tabular, workflows) amal66 · opened 3mo ago · merged 3mo ago by willchen96 amal66 · opened 3mo ago · merged 3mo ago by willchen96 amal66 · opened 3mo ago · merged 3mo ago by willchen96 amal66 · opened 3mo ago · merged 3mo ago by willchen96 amal66 · opened 3mo ago · merged 3mo ago by willchen96 amal66 · opened 3mo ago · merged 3mo ago by willchen96 amal66 · opened 3mo ago · merged 3mo ago by willchen96 #229 [Testing 06] test: unit tests for access control, storage, user API keys and chat doc resolution amal66 · opened 3mo ago · merged 3mo ago #237 [Testing 09] test: unit-cover the highest-risk backend libs + raise the coverage ratchet amal66 · opened 3mo ago · merged 3mo ago by willchen96 amal66 · opened 3mo ago · merged 3mo ago by willchen96 amal66 · opened 3mo ago · merged 3mo ago by willchen96 ⛔ Closed without merge (29)
amal66 · opened 3mo ago · closed 2mo ago #330 fix(schema): re-sync schema.sql with the chats-overview migration; make the drift gate required amal66 · opened 2mo ago · closed 2mo ago #369 [Architecture] feat: default-on durable DB job queue (Postgres) - audit trails, account erasure, storage cleanup, async exports amal66 · opened 2mo ago · closed 2mo ago amal66 · opened 3mo ago · closed 2mo ago #290 feat: first-party Google Drive integration - search and read Drive files from chat (stacked on #285) amal66 · opened 3mo ago · closed 2mo ago amal66 · opened 3mo ago · closed 2mo ago #285 fix: Google Workspace MCP connectors - durable refresh tokens, reliable OAuth, honest connect state (supersedes #185) amal66 · opened 3mo ago · closed 3mo ago #257 [Testing 15] test(evals): offline eval harness - citation accuracy, injection resistance, leakage amal66 · opened 3mo ago · closed 3mo ago amal66 · opened 3mo ago · closed 3mo ago amal66 · opened 3mo ago · closed 3mo ago Show 19 more closed
#261 [Extensibility 3/4] feat: local LLMs via Ollama, behind ENABLE_OLLAMA (stacked on #259) amal66 · opened 3mo ago · closed 3mo ago #260 [Extensibility 2/4] feat: keyless demo mode - a real first-run answer instead of a 401 (stacked on #259) amal66 · opened 3mo ago · closed 3mo ago amal66 · opened 3mo ago · closed 3mo ago amal66 · opened 3mo ago · closed 3mo ago amal66 · opened 4mo ago · closed 3mo ago amal66 · opened 3mo ago · closed 3mo ago #231 [Testing 10] test: offline eval harness - citation accuracy, injection resistance, privilege leakage amal66 · opened 3mo ago · closed 3mo ago amal66 · opened 3mo ago · closed 3mo ago amal66 · opened 3mo ago · closed 3mo ago amal66 · opened 3mo ago · closed 3mo ago amal66 · opened 3mo ago · closed 3mo ago amal66 · opened 3mo ago · closed 3mo ago amal66 · opened 4mo ago · closed 4mo ago amal66 · opened 4mo ago · closed 4mo ago amal66 · opened 4mo ago · closed 4mo ago amal66 · opened 4mo ago · closed 4mo ago amal66 · opened 4mo ago · closed 4mo ago amal66 · opened 4mo ago · closed 4mo ago amal66 · opened 4mo ago · closed 4mo ago