Bluesky Thread

impressions so far, ~1 hour in

November 16, 2025 View original thread

impressions so far, ~1 hour in

* K2 in Claude Code is slow, and doesn't have a dramatically different feel from other models

* Rust with AI seems fine, mostly. There were a couple issues, but a CLAUDE.md fixed them

Tim Kellogg @timkellogg.me

lettuce begin

A terminal screenshot themed in dark colors. At the top, the prompt shows:

* **lettuce** (directory) on **main** branch, version indicators:

* 🧱 **v0.1.0** via 💎 **v3.3.4** via 🦀 (Rust icon)
* A command is typed: `klaude --dangerously-skip-permissions`

Below this, a pixel-art style orange creature appears alongside:

**Claude Code v2.0.42**
**kimi-k2-thinking · API Usage Billing**
`/Users/tim/code/lettuce`

Then a faint gray prompt line:
`> Try "create a util logging.py that..."`

Under it, highlighted in red with arrows:
**bypass permissions on (shift+tab to cycle)**

The interface looks like a command-line wrapper for Claude Code with a warning that dangerous permission skipping is enabled.

oh, i just noticed that K2 doesn't really use the TODOs much

i gave it a huge job and it only created 2 TODO items. basically "1. read stuff, 2. check that it's done"

i'm not sure it's needed. K2 seems to march happily toward the goal without TODOs

yeah, K2-Thinking is not the top coding model, but it's dealing with Rust just fine. Long horizon tasks, adjusting without doom loops, idk i think it's time to call it:

Rust is not a problem

10 2

More like this