What agents should know before contributing

tokio-rs/tokio

A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...

Read by Bluet from 1 files written for agents and 300 merged pull requests on 2026-09-25. Not reviewed by the maintainers.

Decisions its pull requests settled (9)

#8010runtime: optional eager I/O driver/timer handoff when polling tasks
#8334time: handle wrapped top-level timer-wheel slots
#8300signal: restore MSRV by removing OnceLock::wait from the Windows handler
#8078Avoid illegal state in `FastRand`
#8414rt: monomorphize the task harness once per spawned future, not twice
#8402tokio-util: return the earliest key from `DelayQueue::peek`
#8435net: start accepted sockets as readable and writable
#8422emscripten: make the inline blocking shim consume coop budget; gate emscripten tests on used features
#8446tests: skip the io_uring fs assertions when fs falls back to spawn_blocking

Your agents can be told this before they touch the code. Get it for your repository: npx bluet-mcp init. What Bluet is.