DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to chat with Kimi K3 offline and save the transcript with Kimi K3 in C

Run multi-turn chat with the official XTML format on your own CPU, saved to a JSONL file.

  • Research
  • Intermediate
  • 1 h 0 min (excludes the checkpoint download)
  • From the README
  • Any agent

Who it is forA user who wants a private, offline chat session with Kimi K3 and a local record of the conversation.

The problemHosted chat services send every message to a third party, and a model this large is hard to run at home.

The outcomeA REPL session where each turn is answered by Kimi K3, with the full record kept in my-session.jsonl for later use.

What you need first

  • A checkpoint directory of .safetensors shards (1.56 TB on disk for the released checkpoint)
  • A packed trunk directory, created in a step the README excerpt does not show
  • tiktoken.model and tokenizer_config.json in a directory, for text input
  • A machine with a C toolchain for the portable C99 build (build steps are not in the excerpt)
  • An HF_TOKEN environment variable if you use download-model.sh

Steps

  1. Build the engine and download the checkpoint and trunk as described in the batch use case. (inferred, check the README)
  2. ./bin/k3 ~/k3model --trunk ~/k3trunk --preset desktop --tok ~/k3model --chat --system "You are a helpful assistant." --history my-session.jsonl --incremental
  3. Type a message, then use /reset to start over or /exit to quit.
  4. Add --no-think to the same command when you want answers without the thinking block.

Prompt for your agent

In the repo FareedKhan-dev/kimi-k3-in-c, start the --chat REPL with --history <history_file> and --incremental. Send one user message and expect an assistant reply. Verify that the history file contains a user record and an assistant record in JSONL form.

Caveat. The history file can contain every user message and the full assistant reasoning record, so store it as sensitive data.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page