i18ner

Rough naming choice, Kimi K2 already owns that name in most peoples heads

Congrats on the launch, the approach of spending compute upfront is a compelling shift from what the current standard is.

I am curious as to how you handle state invalidation and unseen side-channels during those long-running tasks, because if the agent pauses a task for X days, say waiting for an email reply, but the projects params changed offline or in a channel that the agent has no eyes on, how does the system realize that the pre-compiled context has now gone stale? Does that also mean that proactive actions always require a HITL?