Search
Search docs, blog posts, and ecosystem packages with citations.
Enter a query to see grounded citations.
We can't find the internet
Attempting to reconnect
Jido Ecosystem Digest: May 2026
Maintainer digest of Jido ecosystem activity for May 2026 month to date.
This digest summarizes public Jido ecosystem activity from May 1, 2026 through May 15, 2026. It is generated from the local ecosystem issue and pull request projection, then edited into a reviewable maintainer narrative.
Activity Snapshot
| Metric | Count |
|---|---|
| Merged pull requests | 254 |
| Closed issues | 21 |
| Merged Dependabot pull requests | 149 |
| Open issues at snapshot | 30 |
| Open pull requests at snapshot | 26 |
Pull Request Mix
| Category | Merged PRs |
|---|---|
| Dependency maintenance | 143 |
| CI and workflow | 30 |
| Fixes | 18 |
| Features | 16 |
| Chores | 8 |
| Refactors | 7 |
| Documentation | 1 |
| Other | 31 |
Top Repositories By Merged PRs
| Repo | Merged PRs |
|---|---|
jido_connect | 28 |
req_llm | 28 |
jido_shell | 15 |
jido_ai | 12 |
jido_character | 11 |
jido_action | 10 |
jido_eval | 10 |
jido_studio | 10 |
jido | 9 |
jido_claude | 9 |
jido_evolve | 9 |
ash_jido | 8 |
jido_behaviortree | 8 |
jido_workspace | 8 |
jido_signal | 7 |
Highlights
Workflow Rollout
May started with the v4 shared workflow rollout. The platform release landed in github-actions#6, followed by CI rollout PRs across the package set, including jido#267, jido_action#160, jido_ai#274, req_llm#679, and many smaller adapter packages.
The net effect was a broader, more consistent CI surface across the ecosystem. The rollout also exposed the remaining outliers: jido_bedrock, jido_studio, req_llm, and jido_managed_agents still had dependency or workflow PRs blocked by failed checks, dirty merge states, or missing checks at the May 15 snapshot.
ReqLLM Provider And Runtime Work
req_llm stayed one of the most active repositories. May work covered streaming reliability, provider option coverage, file handling, OpenRouter and xAI behavior, and Bedrock fixes:
| PR | Summary |
|---|---|
| req_llm#661 | Emit terminal error chunks for SSE error events from OpenAI-compatible providers. |
| req_llm#663 | Add reusable OpenAI Responses WebSocket sessions. |
| req_llm#665 | Add OpenRouter session_id support. |
| req_llm#670 | Default token limits from model metadata. |
| req_llm#677 | Support Anthropic uploaded file references. |
| req_llm#680 | Encode OpenRouter file-parser PDFs as files. |
| req_llm#682 | Add Azure reasoning effort and parallel_tool_calls support. |
| req_llm#692 | Clarify Bedrock canonical specs and inference profiles. |
| req_llm#695 | Preserve partial Google usage metadata. |
| req_llm#698 | Allow reasoning effort on the Grok-4 family. |
| req_llm#699 | Expose explicit xAI Responses API routing. |
Several closed issues map directly to this work, including req_llm#664, req_llm#672, req_llm#678, req_llm#690, req_llm#694, and req_llm#696.
Jido AI Runtime And ReAct Follow-Up
jido_ai continued to absorb runtime feedback around streaming, tool calls, signal routing, and ReAct execution:
| PR | Summary |
|---|---|
| jido_ai#271 | Preserve LLM delta ordering metadata. |
| jido_ai#272 | Reuse OpenAI Responses WebSocket sessions. |
| jido_ai#275 | Sanitize unsafe tool response details. |
| jido_ai#276 | Add missing tool_call_id on selected tool call telemetry events. |
| jido_ai#281 | Forward agent signal routes. |
| jido_ai#288 | Ignore benign ReAct stream cancel exits. |
| jido_ai#278 | Add multimodal ReAct query support. |
| jido_ai#279 | Remove DualKeyAccess and fix ex_slop findings. |
The stream-cancel regression was tracked as jido_ai#287 and closed with the ReAct cancellation fix.
Google Workspace Integration In Jido Connect
jido_connect saw a large May burst around Google Drive and Google Meet integration. The work moved from service account auth and Drive permission discovery into watcher and catalog coverage:
| PR | Summary |
|---|---|
| jido_connect#8 | Support Drive permission field discovery. |
| jido_connect#16 | Add Drive watch webhooks. |
| jido_connect#17 | Add Drive revision permission lifecycle support. |
| jido_connect#18 | Add Drive comments, replies, and shared drive handling. |
| jido_connect#23 | Refresh Google catalog docs. |
| jido_connect#30 | Add Google Meet catalog packs. |
Closed issues included jido_connect#5 for end-to-end service account auth and jido_connect#6 for provider-specific Drive permission fields.
Core Jido, Action Catalogs, And Adapter Resumption
Several cross-package capabilities moved forward:
| Area | Links |
|---|---|
| Core plugin lifecycle | jido#278 added plugin phase callbacks with runtime context. |
| Core identity namespace | jido#277 moved identity modules under the agent namespace to unblock the separate jido_identity package. |
| Action catalogs | jido_action#171 added catalog data structures and jido_action#172 added canonical catalog merge behavior. |
| Harness session IDs | jido_harness#27 added RunRequest.session_id. |
| Claude session resumption | jido_claude#23 resumed Claude sessions from harness requests. |
| Codex thread mapping | jido_codex#21 mapped harness session IDs to Codex threads. |
| Ash schema generation | ash_jido#55 included belongs_to source attributes in generated schemas. |
Dependency Maintenance Wave
May also included a major dependency maintenance pass. As of this digest snapshot, 149 Dependabot PRs had merged in May. The heaviest dependency-maintenance repos were jido_shell, jido_character, jido_eval, jido_studio, jido_evolve, req_llm, jido_behaviortree, and jido_workspace.
The May 15 pass alone landed Dependabot updates across jido_character, jido_eval, jido_mcp, jido_memory, jido_messaging, and jido_shell, including:
| Repo | Examples |
|---|---|
jido_shell | #37, #38, #39, #40, #41, #42 |
jido_messaging | #12, #13, #14, #15 |
jido_eval | #7, #8, #9, #10, #11 |
Closed Issues
Open Follow-Ups At Snapshot
These were still open when the digest data was captured.
Actionable Issues
PRs Needing Attention
| Repo | PR | Snapshot state |
|---|---|---|
jido_ai | #286 Agent Skills discovery, activation, diagnostics, and resources | Unstable |
jido_ai | #289 ReAct request transformer model override | Unstable |
jido_bedrock | #5 jido_memory dependency bump | Unstable |
jido_bedrock | #6 ex_doc dependency bump | Unstable |
jido_connect | #3 Drive catalog availability and webhook endpoints | Dirty |
jido_connect | #4 Drive permission embedding fix | Dirty |
jido_managed_agents | #2 v4 workflow rollout | Unstable |
jido_studio | #20 jido_ai 2.1.0 dependency bump | Unstable |
req_llm | #681 OpenTelemetry GenAI semantic conventions | Needs work |
req_llm | #691 Fireworks AI provider | Needs work |
Data Notes
- Window: May 1, 2026 through May 15, 2026, using US Central calendar boundaries.
- Source: local
data/jido.sqliteissue and pull request projection. - Snapshot syncs: full ecosystem sync completed at
2026-05-15T14:10:41Z; targeted post-merge sync completed at2026-05-15T14:18:03Z. - This page is a draft digest for maintainer review. It should be regenerated or reviewed again before publication at the end of the month.