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.

integrationinfrastructure

amal66 has added an official Python toolkit for Mike - the kind of pre-built connector that lets a developer wire Mike's chat, document, and workflow features into their own software in a few lines instead of hand-coding every request. It follows the same conventions Python developers already know from popular AI providers, so anyone who has built against those will feel at home immediately.

The point isn't a single feature - it's the signal. This fork is treating Mike as a platform to build on, not just an app to run, and giving outside teams a clean, supported way to connect. It sits alongside earlier work on a JavaScript equivalent and pluggable extensions, all pointing the same direction.

So what Worth a look for legal-ops and product teams who want Mike talking to their existing tools rather than living in a silo.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from amal66/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date

97b37ca4 feat(python-sdk): httpx-based sync/async client for the Mike API Amal 2026-05-24 ↗ GitHub

SHA	Subject	Author	Date
`97b37ca4`	feat(python-sdk): httpx-based sync/async client for the Mike API	Amal	2026-05-24	↗ GitHub
commit body Adds sdks/python/ - a fully typed Python SDK covering every key API surface so community forks can build integrations without writing HTTP boilerplate from scratch. Structure mirrors the Anthropic and OpenAI Python SDK conventions: - MikeClient / AsyncMikeClient - thin httpx wrappers; swap in a custom httpx client for proxy/testing, pass session_token for auth - Resources: chat, documents, projects, tabular, workflows, user - each exposed as client.<resource>.<verb>() - SyncStream / AsyncStream - iterate SSE events from chat and tabular generate endpoints as plain Python dicts - Pydantic v2 models for every response type; open to model_validate from raw API JSON - Exception hierarchy (MikeError → APIError → AuthenticationError, NotFoundError, RateLimitError, InternalServerError, StreamError) - 15 pytest tests with respx mocking (sync + async paths, error handling) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

commit body

Adds sdks/python/ - a fully typed Python SDK covering every key API
surface so community forks can build integrations without writing HTTP
boilerplate from scratch.

Structure mirrors the Anthropic and OpenAI Python SDK conventions:
- MikeClient / AsyncMikeClient - thin httpx wrappers; swap in a custom
  httpx client for proxy/testing, pass session_token for auth
- Resources: chat, documents, projects, tabular, workflows, user - each
  exposed as client.<resource>.<verb>()
- SyncStream / AsyncStream - iterate SSE events from chat and tabular
  generate endpoints as plain Python dicts
- Pydantic v2 models for every response type; open to model_validate from
  raw API JSON
- Exception hierarchy (MikeError → APIError → AuthenticationError,
  NotFoundError, RateLimitError, InternalServerError, StreamError)
- 15 pytest tests with respx mocking (sync + async paths, error handling)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-601.md from inside the repo you want the changes in.

⬇ Download capture-thread-601.md