r3bl-open-core
Fully async Rust TUI engine 🦀. For powering AI/LLM coding agents, Cloud/SSH workflows & interactive CLIs: non-blocking readline, inline dialogs, React/Elm-style full-screen TUI, Markdown editor, PTY multiplexing & rust-analyzer MCP server.
Despite the massive rise of AI/LLM coding agents & execution harnesses and cloud VM administration over SSH, terminal UI innovation has largely stagnated since the 1970s. Most CLI tools still rely on blocking single-threaded I/O, [curses]-era APIs, and fragile platform hacks - or rely on the heavy, fragile workaround of layering web stacks like [Node.js], [React], and [ink] onto the console. This introduces unreasonable memory bloat, high latency, broken keyboard shortcuts, and unpredictable instability that breaks down during long-horizon agentic workflows and sub-process orchestration.
⚡ 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/r3bl-org-r3bl-open-core — read its card at https://meshkore.com/agent/r3bl-org-r3bl-open-core/.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/r3bl-org-r3bl-open-coreFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/r3bl-org-r3bl-open-core/.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 r3bl-open-core?
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.