sentinel-meet
SentinelOS plugin for SentinelMeet — gives your SentinelOS agent read-only access to your local meeting database: list meetings, pull transcripts and summaries, and search across everything you've ever recorded.
Install
pip install sentinel-meet
SentinelOS discovers the plugin automatically via the sentinel_agent.plugins entry point group — no configuration required. After install, a new 🎙️ sentinelmeet toolset appears in sentinel tools.
Prerequisites
- macOS with the SentinelMeet app installed — download from the releases page.
- Run the app at least once so it creates its database at
~/Library/Application Support/com.apocys.meeting-speech/meeting_minutes.sqlite. - Python ≥ 3.10. Zero runtime dependencies (stdlib only).
If the app/database is absent the tools stay registered but return an install hint instead of failing silently.
Tools
| Tool | What it does |
|---|---|
sentinelmeet_list_meetings |
Recent meetings (most recent first) with transcript segment counts. Optional since (ISO-8601) and limit (1–100, default 20). |
sentinelmeet_get_transcript |
Full transcript of one meeting (meeting_id). Prefers the aggregated transcript when available, otherwise ordered segments with speaker + timestamps. Large payloads are truncated. |
sentinelmeet_get_summary |
Meeting notes (markdown) plus per-segment summaries, action items and key points (meeting_id). |
sentinelmeet_search_transcripts |
Case-insensitive literal text search across all transcripts (query, optional limit). Returns ~200-char excerpts around each match. |
Example (agent-side):
> what did we decide in yesterday's roadmap meeting?
🎙️ sentinelmeet_list_meetings(since="2026-07-07")
🎙️ sentinelmeet_get_summary(meeting_id="…")
Privacy & safety
- Strictly read-only — every connection is opened with SQLite
mode=ro; the plugin can never modify your meeting data. - Local-only — data never leaves your machine; the plugin talks to a local SQLite file and nothing else.
- Parameterised SQL only — no string interpolation, ever.
- Custom DB location: set
SENTINELMEET_DB_PATH=/path/to/meeting_minutes.sqlite.
Development
pip install -e ".[dev]"
pytest
License
MIT — see LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for sentinel-meet 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sentinel_meet-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for sentinel_meet-0.1.0-py3-none-any.whl |
Release files / sentinel_meet-0.1.0-py3-none-any.whl
| Download URL | sentinel_meet-0.1.0-py3-none-any.whl |
|---|---|
| Size | 8.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ea41dfa4ae11177231e882780f293a4b9033b603a59205193198498391b2c9e5
|
|
BLAKE2b-256 checksum How to use checksums |
dbadddc4c3f7d901f50691cf9c19d056d972624a870fbc71e5bf1c1174389b2c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.6
|
Security for sentinel-meet 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
