Vexa-ai/vexa
Open-source meeting transcription API for Google Meet, Microsoft Teams & Zoom. Auto-join bots, real-time WebSocket transcripts, MCP server for AI agents. Self-host or use hosted SaaS.
Is Vexa-ai/vexa beginner-friendly?
The maintainers of Vexa-ai/vexa usually reply to a pull request within 1 day. 21 beginner-friendly issues are open now.
- Stars
- 2.9k
- Forks
- 496
- Open beginner issues
- 21
- Indexed issues
- 536
- Avg merge
- 11h 15m
- Merged PRs (30d)
- 38
- Dominant language
- Python
- License
- Apache-2.0
- Last GitHub push
- Oct 6, 2026
- Latest indexed
- Oct 6, 2026
- Contributing guide
- Contributing guide
- Code of conduct
- No code of conduct
- Beginner labels
- good first issue help wanted
How to contribute to Vexa-ai/vexa
- Read the contributing guide first: it says how the maintainers want changes proposed, tested and reviewed.
- Your contributions will be published under the project's Apache-2.0 license.
- Pick one of the 21 open beginner-friendly issues below and comment that you want to work on it before you start.
Issues somebody may already be working on are listed last. List everything by date
-
Calendar sync: recurring events land a day late when the local start falls on a different UTC dateOpen
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Vexa-ai/vexa#2050 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 70/100
Vexa-ai/vexa#2046 · 1 comment ·
Maintainers usually reply within 1 day
-
[DEV] Teams bots get a joinable link — a bare thread id is refused, 17-digit ids join at /meet/Openstate: prepared type: bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
state: prepared type: bug
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
[Hosted] adding fundOpen
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
Vexa-ai/vexa#1851 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 1-2 days Newbie friendliness 15/100
Vexa-ai/vexa#1847 · 1 comment ·
Maintainers usually reply within 1 day
-
Model choice: operator-declared model catalog behind a provider port, picked per chat in the terminalMay be free again @DmitriyG228 claimed this 32 days ago, and no pull request is open. Openstate: claimed
Vexa-ai/vexa#1796 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
v0.13.2-rc.1: Minutes connections, workspaces and private-source researchMay be free again @DmitriyG228 claimed this 33 days ago, and no pull request is open. Openstate: claimed
Vexa-ai/vexa#1783 · 5 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
[DEV] Zoom on a CPU-starved bot page: keep its speech and its timelineMay be free again @DmitriyG228 claimed this 34 days ago, and no pull request is open. Openstate: awaiting-evaluation type: bug
Vexa-ai/vexa#1782 · 1 assignee ·
Maintainers usually reply within 1 day
-
[DEV] Retrieve named transcripts from native meetings — integrate the operator-supplied SDK backendMay be free again @DmitriyG228 claimed this 35 days ago, and no pull request is open. Openarea: bots lane:contract live-required state: prepared type: feature
Vexa-ai/vexa#1772 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Minutes: optional native CRM records, MCP access and importMay be free again @DmitriyG228 claimed this 39 days ago, and no pull request is open. Openstate: claimed
Vexa-ai/vexa#1762 · 5 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Vexa-ai/vexa#1743 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
type: bug
Difficulty 5/5 Over a week Newbie friendliness 10/100
Vexa-ai/vexa#1716 · 1 comment ·
Maintainers usually reply within 1 day
-
type: feature
Difficulty 4/5 3-5 days Newbie friendliness 20/100
Vexa-ai/vexa#1715 · 1 comment ·
Maintainers usually reply within 1 day
-
gmeet authenticated join: "Join anyway" CTA not matched, structural fallback clicks the Gemini "Start" buttonPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Terminal: pasting a Teams link with a malformed %-escape throws URIError — Send bot silently does nothingPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Vexa-ai/vexa#2011 · 1 comment ·
Maintainers usually reply within 1 day
-
Webhook retry: a 4xx on a retried delivery is acked as delivered — the envelope vanishes without a dead-letter record or logPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 3/5 1-2 days Newbie friendliness 62/100
Vexa-ai/vexa#2009 · 1 comment ·
Maintainers usually reply within 1 day
-
A bot live across a meeting-api version swap is billed $0 (service_provenance_missing)Possibly taken @DmitriyG228 claimed this 10 days ago. Openbug
Vexa-ai/vexa#1974 · 1 assignee ·
Maintainers usually reply within 1 day
-
Dashboard live transcript: the grey draft jumps between unrelated phrases, and the confirmed line lands as different textPossibly taken @DmitriyG228 claimed this 10 days ago. Openbug
Vexa-ai/vexa#1973 · 1 assignee ·
Maintainers usually reply within 1 day
-
[DEV] Verify the bot speaks and posts in every meeting platform (Meet, Zoom web, Teams) on the stationPossibly taken @DmitriyG228 claimed this 10 days ago. Open
Vexa-ai/vexa#1970 · 1 assignee ·
Maintainers usually reply within 1 day
-
[DEV] dashboard: standard hardening response headersPossibly taken @DmitriyG228 claimed this 10 days ago. Open
Vexa-ai/vexa#1969 · 1 assignee ·
Maintainers usually reply within 1 day
-
[DEV] meeting-api: list_meetings and /bots/status served by indexes (0.13.4 attempt 3)Possibly taken @DmitriyG228 claimed this 10 days ago. Openbug
Vexa-ai/vexa#1968 · 1 assignee ·
Maintainers usually reply within 1 day
-
Load rehearsal before every prod pin: one hour of real prod traffic against the candidate on the prod dumpPossibly taken @DmitriyG228 claimed this 10 days ago. Open
Vexa-ai/vexa#1966 · 1 assignee ·
Maintainers usually reply within 1 day
-
Meetings list sort is served by an index, not by reading `data` on every rowPossibly taken @DmitriyG228 claimed this 10 days ago. Open
Vexa-ai/vexa#1965 · 1 assignee ·
Maintainers usually reply within 1 day
-
Public GET /status and an X-Vexa-Maintenance header on every API reply during maintenancePossibly taken @DmitriyG228 claimed this 11 days ago. Open
Vexa-ai/vexa#1964 · 1 assignee ·
Maintainers usually reply within 1 day
-
Teams: one participant's speech stays unnamed for most of a call (three prod meetings hold 95% of unnamed Teams speech)Possibly taken @DmitriyG228 claimed this 11 days ago. Openbug
Vexa-ai/vexa#1963 · 1 assignee ·
Maintainers usually reply within 1 day
-
Per-account ramp limit beside the concurrency ceiling (the "flexible raise")Possibly taken @DmitriyG228 claimed this 11 days ago. Openfeature
Vexa-ai/vexa#1962 · 1 assignee ·
Maintainers usually reply within 1 day
-
Bot posts a message in the meeting chat when it is admitted (chat_on_join)Possibly taken @DmitriyG228 claimed this 11 days ago. Openfeature
Vexa-ai/vexa#1961 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Verify station: the test Meet room has no speaker, so 'transcript returns 200 with segments' cannot be observedPossibly taken @DmitriyG228 claimed this 11 days ago. Openbug
Vexa-ai/vexa#1960 · 1 assignee ·
Maintainers usually reply within 1 day
-
release-value-gate.mjs has no test: #1935 acceptance 4 (promote value-gate passes an all-green batch with no labels, exits 1 on a red runtime PR) cannot be checkedPossibly taken @DmitriyG228 claimed this 11 days ago. Openbug
Vexa-ai/vexa#1959 · 1 assignee ·
Maintainers usually reply within 1 day
-
1935 has not landed on main: merge-card, release value-gate and governance docs still need/mention `state: value-signed`Possibly taken @DmitriyG228 claimed this 11 days ago. Openbug
Vexa-ai/vexa#1958 · 1 assignee ·
Maintainers usually reply within 1 day
-
Build host run-tests cannot run bot tests that import @vexa/join (dist not built)Possibly taken @DmitriyG228 claimed this 11 days ago. Openbug
Vexa-ai/vexa#1955 · 1 assignee ·
Maintainers usually reply within 1 day
-
v0.13.4 line head b5ad133: required checks merge-card/static/python/node never ran; PR #1863 is DIRTY and DCO failsPossibly taken @DmitriyG228 claimed this 11 days ago. Openbug
Vexa-ai/vexa#1954 · 1 assignee ·
Maintainers usually reply within 1 day
-
station-key cannot mint scoped keys, so tx-only / browser-only acceptance can't be observed on the 0.13.4 stationPossibly taken @DmitriyG228 claimed this 11 days ago. Openbug
Vexa-ai/vexa#1953 · 1 assignee ·
Maintainers usually reply within 1 day
-
Gateway test: a tx-only key's /bot-accounts/sessions/{sid}/vnc socket is not closed 4403Possibly taken @DmitriyG228 claimed this 11 days ago. Openbug
Vexa-ai/vexa#1952 · 1 assignee ·
Maintainers usually reply within 1 day
-
Confirm required checks (merge-card, static, python, node) on codex/v0.13.4 head b5ad133Possibly taken @DmitriyG228 claimed this 11 days ago. Openbug
Vexa-ai/vexa#1951 · 1 assignee ·
Maintainers usually reply within 1 day
-
run-tests job does not install dependencies, so npm test in core/meetings/modules/join and the bot join-evidence test cannot runPossibly taken @DmitriyG228 claimed this 11 days ago. Openbug
Vexa-ai/vexa#1950 · 1 assignee ·
Maintainers usually reply within 1 day
-
Stage station 0.13.4: outside-caller check of Meet bot admission needs a stage API keyPossibly taken @DmitriyG228 claimed this 11 days ago. Openbug
Vexa-ai/vexa#1949 · 1 assignee ·
Maintainers usually reply within 1 day
-
1935 acceptance-6: governance docs still say 'attestation signer' (delivery.mdx:403)Possibly taken @DmitriyG228 claimed this 11 days ago. Openbug
Vexa-ai/vexa#1948 · 1 assignee ·
Maintainers usually reply within 1 day
-
Gateway VNC relay: no test shows a tx-only key is not closed 4403Possibly taken @DmitriyG228 claimed this 11 days ago. Openbug
Vexa-ai/vexa#1947 · 1 assignee ·
Maintainers usually reply within 1 day
-
test_transcript_owner_scope: cover the remaining #1922 C1/C2 routes (own DELETE /meetings 2xx, cross-user GET/DELETE /meetings/{id}, DELETE /recordings/{id})Possibly taken @DmitriyG228 claimed this 11 days ago. Openbug
Vexa-ai/vexa#1946 · 1 assignee ·
Maintainers usually reply within 1 day
-
Stage station: a way for the acceptance verifier to get scoped test keys without the admin secretPossibly taken @DmitriyG228 claimed this 11 days ago. Openbug
Vexa-ai/vexa#1945 · 1 assignee ·
Maintainers usually reply within 1 day
-
1922 C6: 403 'Insufficient scope' docs rows do not say that only a browser-only key gets itPossibly taken @DmitriyG228 claimed this 11 days ago. Openbug
Vexa-ai/vexa#1944 · 1 assignee ·
Maintainers usually reply within 1 day
-
1922 C2: cross-user GET /meetings/{id}, DELETE /meetings/{id} and DELETE /recordings/{id} are not shown to return 403/404 for a bot-only keyPossibly taken @DmitriyG228 claimed this 11 days ago. Openbug
Vexa-ai/vexa#1943 · 1 assignee ·
Maintainers usually reply within 1 day
-
1922 C1: no check shows a quickstart bot-only key gets 2xx on POST /bots and on DELETE /meetings/{id} for its own meetingPossibly taken @DmitriyG228 claimed this 11 days ago. Openbug
Vexa-ai/vexa#1942 · 1 assignee ·
Maintainers usually reply within 1 day
-
Write the literal acceptance-6 grep pattern into #1935 so it can be re-run exactlyPossibly taken @DmitriyG228 claimed this 11 days ago. Openbug
Vexa-ai/vexa#1941 · 1 assignee ·
Maintainers usually reply within 1 day
Showing the newest 100
This page lists what was indexed most recently. Advanced filter has the whole inventory, narrowed by language, difficulty and how long a task takes.