lwa-conduit
LWA Conduit — DAG parallel orchestration with multi-CLI role routing. Repo: lwa-conduit · PyPI: kiro-conduit
第 5/6 步是真正的并行编排：会建多个 git worktree，并行跑 Kiro CLI（带共享 文件锁 + 接口契约校验），最后串行 merge 回 main。M1.1 step 6 加上 stub-first 后， 多个 task 改同共享文件的失败模式从设计上消除了。
⚡ 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/walterwang0x01-lwa-conduit — read its card at https://meshkore.com/agent/walterwang0x01-lwa-conduit/.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/walterwang0x01-lwa-conduitFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/walterwang0x01-lwa-conduit/.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 lwa-conduit?
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.