%{
  title: "Jido Ecosystem Digest: May 2026",
  description: "Maintainer digest of Jido ecosystem activity for May 2026 month to date.",
  category: :docs,
  legacy_paths: [],
  tags: [:docs, :contributors, :ecosystem, :digest],
  order: 25,
  menu_label: "May 2026 Digest"
}
---

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](https://github.com/agentjido/github-actions/pull/6), followed by CI rollout PRs across the package set, including [jido#267](https://github.com/agentjido/jido/pull/267), [jido_action#160](https://github.com/agentjido/jido_action/pull/160), [jido_ai#274](https://github.com/agentjido/jido_ai/pull/274), [req_llm#679](https://github.com/agentjido/req_llm/pull/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](https://github.com/agentjido/req_llm/pull/661) | Emit terminal error chunks for SSE error events from OpenAI-compatible providers. |
| [req_llm#663](https://github.com/agentjido/req_llm/pull/663) | Add reusable OpenAI Responses WebSocket sessions. |
| [req_llm#665](https://github.com/agentjido/req_llm/pull/665) | Add OpenRouter `session_id` support. |
| [req_llm#670](https://github.com/agentjido/req_llm/pull/670) | Default token limits from model metadata. |
| [req_llm#677](https://github.com/agentjido/req_llm/pull/677) | Support Anthropic uploaded file references. |
| [req_llm#680](https://github.com/agentjido/req_llm/pull/680) | Encode OpenRouter file-parser PDFs as files. |
| [req_llm#682](https://github.com/agentjido/req_llm/pull/682) | Add Azure reasoning effort and `parallel_tool_calls` support. |
| [req_llm#692](https://github.com/agentjido/req_llm/pull/692) | Clarify Bedrock canonical specs and inference profiles. |
| [req_llm#695](https://github.com/agentjido/req_llm/pull/695) | Preserve partial Google usage metadata. |
| [req_llm#698](https://github.com/agentjido/req_llm/pull/698) | Allow reasoning effort on the Grok-4 family. |
| [req_llm#699](https://github.com/agentjido/req_llm/pull/699) | Expose explicit xAI Responses API routing. |

Several closed issues map directly to this work, including [req_llm#664](https://github.com/agentjido/req_llm/issues/664), [req_llm#672](https://github.com/agentjido/req_llm/issues/672), [req_llm#678](https://github.com/agentjido/req_llm/issues/678), [req_llm#690](https://github.com/agentjido/req_llm/issues/690), [req_llm#694](https://github.com/agentjido/req_llm/issues/694), and [req_llm#696](https://github.com/agentjido/req_llm/issues/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](https://github.com/agentjido/jido_ai/pull/271) | Preserve LLM delta ordering metadata. |
| [jido_ai#272](https://github.com/agentjido/jido_ai/pull/272) | Reuse OpenAI Responses WebSocket sessions. |
| [jido_ai#275](https://github.com/agentjido/jido_ai/pull/275) | Sanitize unsafe tool response details. |
| [jido_ai#276](https://github.com/agentjido/jido_ai/pull/276) | Add missing `tool_call_id` on selected tool call telemetry events. |
| [jido_ai#281](https://github.com/agentjido/jido_ai/pull/281) | Forward agent signal routes. |
| [jido_ai#288](https://github.com/agentjido/jido_ai/pull/288) | Ignore benign ReAct stream cancel exits. |
| [jido_ai#278](https://github.com/agentjido/jido_ai/pull/278) | Add multimodal ReAct query support. |
| [jido_ai#279](https://github.com/agentjido/jido_ai/pull/279) | Remove `DualKeyAccess` and fix `ex_slop` findings. |

The stream-cancel regression was tracked as [jido_ai#287](https://github.com/agentjido/jido_ai/issues/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](https://github.com/agentjido/jido_connect/pull/8) | Support Drive permission field discovery. |
| [jido_connect#16](https://github.com/agentjido/jido_connect/pull/16) | Add Drive watch webhooks. |
| [jido_connect#17](https://github.com/agentjido/jido_connect/pull/17) | Add Drive revision permission lifecycle support. |
| [jido_connect#18](https://github.com/agentjido/jido_connect/pull/18) | Add Drive comments, replies, and shared drive handling. |
| [jido_connect#23](https://github.com/agentjido/jido_connect/pull/23) | Refresh Google catalog docs. |
| [jido_connect#30](https://github.com/agentjido/jido_connect/pull/30) | Add Google Meet catalog packs. |

Closed issues included [jido_connect#5](https://github.com/agentjido/jido_connect/issues/5) for end-to-end service account auth and [jido_connect#6](https://github.com/agentjido/jido_connect/issues/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](https://github.com/agentjido/jido/pull/278) added plugin phase callbacks with runtime context. |
| Core identity namespace | [jido#277](https://github.com/agentjido/jido/pull/277) moved identity modules under the agent namespace to unblock the separate `jido_identity` package. |
| Action catalogs | [jido_action#171](https://github.com/agentjido/jido_action/pull/171) added catalog data structures and [jido_action#172](https://github.com/agentjido/jido_action/pull/172) added canonical catalog merge behavior. |
| Harness session IDs | [jido_harness#27](https://github.com/agentjido/jido_harness/pull/27) added `RunRequest.session_id`. |
| Claude session resumption | [jido_claude#23](https://github.com/agentjido/jido_claude/pull/23) resumed Claude sessions from harness requests. |
| Codex thread mapping | [jido_codex#21](https://github.com/agentjido/jido_codex/pull/21) mapped harness session IDs to Codex threads. |
| Ash schema generation | [ash_jido#55](https://github.com/agentjido/ash_jido/pull/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](https://github.com/agentjido/jido_shell/pull/37), [#38](https://github.com/agentjido/jido_shell/pull/38), [#39](https://github.com/agentjido/jido_shell/pull/39), [#40](https://github.com/agentjido/jido_shell/pull/40), [#41](https://github.com/agentjido/jido_shell/pull/41), [#42](https://github.com/agentjido/jido_shell/pull/42) |
| `jido_messaging` | [#12](https://github.com/agentjido/jido_messaging/pull/12), [#13](https://github.com/agentjido/jido_messaging/pull/13), [#14](https://github.com/agentjido/jido_messaging/pull/14), [#15](https://github.com/agentjido/jido_messaging/pull/15) |
| `jido_eval` | [#7](https://github.com/agentjido/jido_eval/pull/7), [#8](https://github.com/agentjido/jido_eval/pull/8), [#9](https://github.com/agentjido/jido_eval/pull/9), [#10](https://github.com/agentjido/jido_eval/pull/10), [#11](https://github.com/agentjido/jido_eval/pull/11) |

## Closed Issues

| Repo | Issue | Closed |
| --- | --- | --- |
| `req_llm` | [#696 Bedrock streaming bypasses `req_http_options` plugins](https://github.com/agentjido/req_llm/issues/696) | May 14 |
| `jido_connect` | [#6 Support provider-specific Drive permission field discovery](https://github.com/agentjido/jido_connect/issues/6) | May 14 |
| `jido_connect` | [#5 Add end-to-end Google service account auth support](https://github.com/agentjido/jido_connect/issues/5) | May 14 |
| `jido_ai` | [#287 ReAct stream cancel exits with `:noproc`](https://github.com/agentjido/jido_ai/issues/287) | May 14 |
| `req_llm` | [#690 Amazon Bedrock warts](https://github.com/agentjido/req_llm/issues/690) | May 13 |
| `req_llm` | [#694 Gemini partial usage metadata zeros the usage struct](https://github.com/agentjido/req_llm/issues/694) | May 13 |
| `jido` | [#276 Rename core identity namespace](https://github.com/agentjido/jido/issues/276) | May 13 |
| `llm_db` | [#188 Retire Gemini 3.1 Flash Lite Preview](https://github.com/agentjido/llm_db/issues/188) | May 13 |
| `jido_action` | [#170 Add first-class action catalog and metadata registry](https://github.com/agentjido/jido_action/issues/170) | May 13 |
| `ash_jido` | [#54 `belongs_to` source attributes are dropped from generated tool schema](https://github.com/agentjido/ash_jido/issues/54) | May 8 |
| `jido_action` | [#162 `convert_params_using_schema/2` bug](https://github.com/agentjido/jido_action/issues/162) | May 8 |
| `jido_claude` | [#21 Resume Claude sessions when request carries `session_id`](https://github.com/agentjido/jido_claude/issues/21) | May 8 |
| `jido_harness` | [#25 Add optional `session_id` to `RunRequest`](https://github.com/agentjido/jido_harness/issues/25) | May 8 |
| `req_llm` | [#678 OpenRouter file-parser PDF content part support](https://github.com/agentjido/req_llm/issues/678) | May 8 |
| `jido_ai` | [#280 `use Jido.AI.Agent` does not support extra `signal_routes`](https://github.com/agentjido/jido_ai/issues/280) | May 6 |
| `req_llm` | [#672 Anthropic `file_id` references](https://github.com/agentjido/req_llm/issues/672) | May 6 |
| `req_llm` | [#669 Default token limit should use model output metadata](https://github.com/agentjido/req_llm/issues/669) | May 5 |
| `github-actions` | [#5 Track v4 reusable Elixir CI platform and pilot rollout](https://github.com/agentjido/github-actions/issues/5) | May 2 |
| `req_llm` | [#664 OpenRouter `session_id` support](https://github.com/agentjido/req_llm/issues/664) | May 1 |

## Open Follow-Ups At Snapshot

These were still open when the digest data was captured.

### Actionable Issues

| Repo | Issue |
| --- | --- |
| `jido` | [#244 Logging and observability standardization across decoupled `jido_*` repos](https://github.com/agentjido/jido/issues/244) |
| `jido` | [#262 Align `Jido.Error` public payloads with observability/error reporting standards](https://github.com/agentjido/jido/issues/262) |
| `jido` | [#263 Make `Jido.Observe` the canonical observability boundary](https://github.com/agentjido/jido/issues/263) |
| `jido_ai` | [#264 Move AI runtime error contract ownership into `Jido.AI.Error`](https://github.com/agentjido/jido_ai/issues/264) |
| `jido_ai` | [#265 Add bounded transport and telemetry sanitization for AI observability payloads](https://github.com/agentjido/jido_ai/issues/265) |
| `jido_run` | [#117 Fix unavailable Weather tool modules in the AI agent with tools tutorial](https://github.com/agentjido/jido_run/issues/117) |

### PRs Needing Attention

| Repo | PR | Snapshot state |
| --- | --- | --- |
| `jido_ai` | [#286 Agent Skills discovery, activation, diagnostics, and resources](https://github.com/agentjido/jido_ai/pull/286) | Unstable |
| `jido_ai` | [#289 ReAct request transformer model override](https://github.com/agentjido/jido_ai/pull/289) | Unstable |
| `jido_bedrock` | [#5 jido_memory dependency bump](https://github.com/agentjido/jido_bedrock/pull/5) | Unstable |
| `jido_bedrock` | [#6 ex_doc dependency bump](https://github.com/agentjido/jido_bedrock/pull/6) | Unstable |
| `jido_connect` | [#3 Drive catalog availability and webhook endpoints](https://github.com/agentjido/jido_connect/pull/3) | Dirty |
| `jido_connect` | [#4 Drive permission embedding fix](https://github.com/agentjido/jido_connect/pull/4) | Dirty |
| `jido_managed_agents` | [#2 v4 workflow rollout](https://github.com/agentjido/jido_managed_agents/pull/2) | Unstable |
| `jido_studio` | [#20 jido_ai 2.1.0 dependency bump](https://github.com/agentjido/jido_studio/pull/20) | Unstable |
| `req_llm` | [#681 OpenTelemetry GenAI semantic conventions](https://github.com/agentjido/req_llm/pull/681) | Needs work |
| `req_llm` | [#691 Fireworks AI provider](https://github.com/agentjido/req_llm/pull/691) | Needs work |

## Data Notes

- Window: May 1, 2026 through May 15, 2026, using US Central calendar boundaries.
- Source: local `data/jido.sqlite` issue and pull request projection.
- Snapshot syncs: full ecosystem sync completed at `2026-05-15T14:10:41Z`; targeted post-merge sync completed at `2026-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.