Build fails: pinned git deps (jido_ai, jido_messaging) refs no longer exist upstream

[ortegacmanuel]

Problem

Fresh mix deps.get fails because the pinned git refs in mix.exs no longer exist in the upstream Jido repos (likely force-pushed/rebased away):

{:jido_ai, github: "agentjido/jido_ai", ref: "764bb6d", override: true}
{:jido_messaging, github: "agentjido/jido_messaging", ref: "96e62c7"}

fatal: reference is not a tree: 764bb6d61bef4d693376bf9ee9daf6665dd5fcaa
** (Mix) Command "git --git-dir=.git checkout --force --quiet 764bb6d..." failed

What I tried

1. Switch to branch: "main" for all three git deps — deps resolve but jido_browser ~> 0.8 conflicts with jido_action ~> 2.2 required by latest jido_ai.

2. Bump jido_browser to ~> 2.0 and jido to ~> 2.1 — deps resolve and fetch, but compile fails at use Jido.AI.ReActAgent (macro API changed in jido_ai main).

Likely fix needed

• Update mix.exs to use latest compatible Jido ecosystem (jido ~> 2.1, jido_ai main, jido_browser ~> 2.0)
• Adapt Goodwizard.Agent and potentially other modules to the new Jido.AI.ReActAgent macro API
• Update mix.lock with working dependency set

Environment

• Elixir 1.18 / OTP 27
• Docker build with elixir:1.18-otp-27-slim
• Clean clone, no existing deps or _build

Context

I'm trying to deploy Goodwizard as a personal assistant (Telegram channel). Happy to contribute the fix as a PR if you can point me to what changed in the ReActAgent API.

[ortegacmanuel]

Update: Full resolution and working deployment

I managed to get Goodwizard building and running on Telegram with the latest Jido ecosystem. Here's everything I found and fixed. Happy to open a PR with these changes.

Root Cause

The upstream Jido repos force-pushed their history, deleting the pinned git refs:

Dep	Pinned ref	Status
jido_ai	764bb6d	Gone — repo rewritten, only 50 shallow commits remain
jido_messaging	96e62c7	Exists in full clone (37 commits) but not in shallow clone. Entire repo was rewritten to a single squash commit on main
jido_character	20ae4ef	Still exists (current HEAD)

Changes needed (5 areas)

1. Dependency versions (mix.exs)

# Before (broken — refs don't exist)
{:jido, "~> 2.0.0-rc", override: true},
{:jido_ai, github: "agentjido/jido_ai", ref: "764bb6d", override: true},
{:jido_character, github: "agentjido/jido_character", ref: "20ae4ef"},
{:jido_browser, "~> 0.8", override: true},
{:jido_messaging, github: "agentjido/jido_messaging", ref: "96e62c7"},

# After (working)
{:jido, "~> 2.1", override: true},
{:jido_ai, github: "agentjido/jido_ai", branch: "main", override: true},
{:jido_character, github: "agentjido/jido_character", branch: "main"},
{:jido_browser, "~> 2.0", override: true},
{:jido_messaging, path: "deps_vendored/jido_messaging", override: true},  # see below

Note: jido_messaging must be vendored because the new main completely removed the Channels.Telegram.Handler API that Goodwizard depends on.

2. Agent macro rename (agent.ex, sub_agent.ex)

# Before
use Jido.AI.ReActAgent,

# After
use Jido.AI.Agent,

Jido.AI.ReActAgent no longer exists in jido_ai main. The new module is Jido.AI.Agent with the same options (name, tools, model, plugins, etc.).

3. JidoBrowser namespace rename (27 files)

Global rename across all browser action wrappers:

JidoBrowser.Plugin        → Jido.Browser.Plugin
JidoBrowser.Actions.*     → Jido.Browser.Actions.*
JidoBrowser.Session       → Jido.Browser.Session
JidoBrowser.Adapters.*    → Jido.Browser.Adapters.*

jido_browser 2.0 moved from JidoBrowser to Jido.Browser namespace.

4. JidoMessaging vendoring

The jido_messaging repo was completely rewritten — the old Channels.Telegram.Handler macro that Goodwizard uses no longer exists in main. The new version uses a BridgePlugin + Instance + Ingest architecture.

Workaround: Vendor jido_messaging at the old commit 96e62c7 (still recoverable via full git clone). Place in deps_vendored/jido_messaging/ and reference as path: dep.

The vendored demo code references Jido.AI.ReActAgent which also doesn't exist, so deps_vendored/jido_messaging/lib/jido_messaging/demo/ and lib/mix/ should be deleted from the vendored copy.

5. Model configuration

The model: option in use Jido.AI.Agent is set at compile time and the runtime config (GOODWIZARD_MODEL env var / config.toml) doesn't override it for the ReAct strategy. The agent always uses the model from the macro, not from config. This means changing the model requires editing agent.ex and sub_agent.ex directly.

This might be intentional but seems like a gap — the config system reads GOODWIZARD_MODEL and reports it in logs, but the ReAct strategy ignores it.

Runtime issue: jido_browser 2.0 JSON encoding crash

After deployment, when the LLM tries to use browser tools (e.g., browser_navigate), the agent crashes with:

(Protocol.UndefinedError) protocol Jason.Encoder not implemented for 
type Jido.Browser.Error.InvalidError (a struct)

The Jido.Browser.Error.InvalidError struct from jido_browser 2.0 doesn't implement Jason.Encoder, but jido_ai's ReAct strategy tries to JSON-encode tool results (including errors). This crashes the agent process.

Impact: Non-blocking for text-only chat (Telegram), but any query where the LLM decides to use browser tools will crash.

Likely fix: Either jido_browser 2.0 needs @derive Jason.Encoder on its error structs, or jido_ai's Turn.encode_tool_result_envelope needs to handle non-encodable structs gracefully.

Working fork

I have a working fork at gazpachoteam/goodwizard with all the above fixes applied. Two instances deployed and running on Telegram (Docker Compose on a DigitalOcean droplet). Happy to open a PR if you'd like these changes upstream.

Suggested path forward

1. Short-term: Apply the 5 changes above to get a buildable, deployable Goodwizard
2. Medium-term: Rewrite the Telegram channel integration to use the new jido_messaging BridgePlugin API (eliminates the vendor)
3. Ask Jido maintainer: Request tagged releases or hex packages for jido_ai, jido_character, jido_messaging so pinned refs aren't needed. Force-pushing history breaks all downstream consumers.