Is the some chat for the project or is all work being cordenated here in github?

[wviana]

你好

I've noticed the project is going really fast, I wonder if there is some more places you folks are chatting while working on features.

I think most of the contributors are Chinese speakers, and english is also not my first language. I'm studding mandarin for some time now, but I'm still far from being able to write and read as I can do for english.

I've noticed that was a big change on the project recently, by moving into a rust implementation, at leas on the TUI part of it. It got me from surprise. So because of it I'm wondering if you are keeping a more "online" chat going on at some channel.

I'm not worried if the main language on it being mandarin, i don't worry about having to keep translating back and forth to be able to communicate. I even think it would be nice to me to learn the language.

[esengine]

你好 — thanks for reaching out, and apologies for the quiet on the chat side.

Right now there isn't one — everything has been happening here in GitHub issues/discussions. I'm planning to open a Discord server with the next release so contributors and users have a real-time place to talk. I'll link it in the README once it's up.

On the Rust move: that was an experiment on my part, and the surprise you felt was fair — I should have signaled it better. In practice the TS ↔ Rust interop wasn't a clean fit for this project. The bridge layer between the Node side and the Rust renderer became a significant maintenance cost, and as effectively a solo maintainer I can't afford to keep paying it. So I've rolled the Rust renderer out and gone back to pure Ink.

Going forward I won't be putting much of my own time into the render layer or visual polish — those are honestly not my strengths, and every hour I spend there is an hour off the core architecture and reliability work that I think matters more for this project. I'd like to hand TUI direction over to contributors who actually have an eye for it. PRs and proposals in that area are very welcome.

Language is no barrier — feel free to write in English here or on Discord when it's up, and don't worry about back-and-forth translation.

[wviana]

About the UI, I'm working on steering feature here. Similar to what exists on claude, you can send messages to be added into the context as soon as the next response stream ends. For example, when you notice the model is going in a way you don't like you can just write some more instructions and it will be queued and used as soon as possible. I almost have it done here. I did it only for ink for now.

[esengine]

Oh that's exactly the feature I want — being able to queue a steering message mid-stream and have it land at the next turn boundary is one of the things I've missed most coming from Claude. I'd love to have it in the project.

Please do open a PR against main whenever you're ready. Ink-only is completely fine — that's the only renderer now anyway. Don't worry about polish or matching any particular code style on the first pass; I'd rather see the design land and iterate from there.

Happy to review as soon as it's up. Thanks for picking this one up.

[wviana]

Yeah, there is another thing on the rust one that would be supporting different arch. For example, today I can run reasonix on android using termux as node interpreter is available everywhere. If we intent to ship the compiled binary (from rust) on android it would require to have a new build for it. Just if we start to distribute using cargo. I think that when you do cargo install it does download source-code an compile it. It takes longer but then we wouldn't have to keep shipping binaries.

Anyway, I really like the rust idea, we could create a discussion only about it so we can start to discuss about details so we can figure out together if it worth it or not.

[wviana]

Oh that's exactly the feature I want — being able to queue a steering message mid-stream and have it land at the next turn boundary is one of the things I've missed most coming from Claude. I'd love to have it in the project.
Please do open a PR against main whenever you're ready. Ink-only is completely fine — that's the only renderer now anyway. Don't worry about polish or matching any particular code style on the first pass; I'd rather see the design land and iterate from there.
Happy to review as soon as it's up. Thanks for picking this one up.

Awesome, I'll try to wrap up on it here before going to bed.

[wviana]

I'll try to wrap up on it here before going to bed.

I couldn't do it. After the rebase I was testing before generating the PR description and opening it and found it very broken.

I pushed as is at this branch https://github.com/wviana/reasonix/tree/feat/steering-queue-messages-while-reponse-streams

feel free to pull it to you local and test and even try to fix it. It's pretty late here.

Let me know if you worked on it at all or not. If I don't get anything back I'll assume you didn't and I'll try to get it back working when I get some time. But I don't know when I will have time tomorrow.