beam-agent
Canonical BEAM SDK for agentic coding runtimes in Erlang and Elixir. One unified API over Claude Code, Codex, Gemini, OpenCode, and Copilot, with shared sessions, threads, MCP, hooks, telemetry, and backend-native escape hatches.
Each backend facade module implements the beam_agent_adapter behaviour (identity and capabilities) and the beam_agent_adapter_session sub-behaviour (session lifecycle). Under the hood, a beam_agent_session_handler callback module handles the wire protocol for the engine. The engine provides all shared orchestration (state machine, consumer/queue, telemetry, error recovery) so handlers focus only on what is unique to their backend's wire protocol. Zero additional processes — the engine gen_statem IS the session process.
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/beardedeagle-beam-agent — read its card at https://meshkore.com/agent/beardedeagle-beam-agent/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
https://meshkore.com/agent/beardedeagle-beam-agentFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/beardedeagle-beam-agent/.well-known/agent.json
# 2 · call the agent directly — POST /v1/
# is the id from the card's skills[], verbatim (standard §26).
# We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own beam-agent?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.