Resources04 · Open ecosystem

COMMUNITY / OPEN ECOSYSTEM

Start in the open ecosystem and place every contribution at the right boundary

The client source provides IM and Agent composition entry points. Kyormar-DevTools opens observation and debugging for events, state, tools, and module communication

01Kyormar-GPUI

Kyormar Client

Native desktop, IM and Agent module entry points, windows, and visible interaction

Start here
Improve the client experience or contribute to IM and Agent composition entry points
Open public repository
02Kyormar-DevTools

DevTools

Open-source event inspector, state traces, tool-call observation, IM ↔ Agent communication debugging, and developer workbench

Start here
Reproduce interaction issues, inspect data provenance, trace tools and module communication, and build new diagnostics
Open public repository
03CLOSED SOURCE / REMOTE

Rust Service

Provides account and selected remote team capabilities; outside the open-source client scope

Start here
Decide only whether remote capabilities are needed; internal service architecture is not required
View boundary note

OPEN PRACTICE / MERGED WORKSHOPS

Workshops are no longer a separate route;
they belong to the open contribution process

Every practice session starts from a real problem and leaves behind its process, outcome, and next step; engineering notes continue under the corresponding issue

01 / Individual / small team

Agent × IM workflow

Bring a real task from Agent execution and verification through IM progress, approval, and results

Propose a practice topic
02 / Team / developer

Agent collaboration and toolchains

Reproduce a multi-Agent or tool-call issue and identify its state source, failure boundary, and repeatable verification steps

Propose a practice topic
03 / Individual / team

Communication-preference practice

Express information density, tone, and reminders as adjustable preferences—not as diagnosis or scoring from a personality questionnaire

Propose a practice topic

CONTRIBUTION CONTRACT

A reproducible issue
is more valuable than a vague conclusion

  1. 01

    Describe the visible symptom

    State what you actually saw or did without deciding the root cause for the system

  2. 02

    Provide the minimal path

    Document the entry point, action, expected result, and actual result so others can reproduce it

  3. 03

    Identify the state source

    When known, identify whether state comes from the client, IM, Agent, or data exchanged between them

  4. 04

    Attach verification evidence

    Distinguish tests, logs, screenshots, and real delivery acceptance