Product news: Claude Code 2.1.234 improves project transcript controls and review ergonomics

Anthropic's Claude Code 2.1.234 release includes two modest controls that reveal larger governance questions. A CLAUDE_CODE_PROJECT_DIR_NAME environment variable lets hosts that assign each session a separate configuration directory choose a shorter name for the per-project transcript directory. A selection:clear keybinding action lets users bind a key to clear an in-application text selection. The release also includes fixes for reliability and interface behavior.

Transcript naming sounds administrative, but a transcript can contain prompts, source excerpts, file paths, code, errors, and model responses. In a school or research environment, some of that material may be confidential, copyrighted, personally identifiable, or security-sensitive. A convenient directory name should never be confused with a retention policy. Institutions need to know where transcripts are stored, which project and user own them, who can read them, whether they synchronize or back up, and when they are deleted. Names should help attribution without embedding student names or sensitive project details.

The selection-clearing action concerns review ergonomics. Keyboard users may select text while examining a long response, and a predictable way to clear that state can reduce accidental actions or confusion. Configurable keybindings can also support individual workflows. Accessibility cannot be inferred from one new command, however. Institutions should test screen-reader announcements, focus order, contrast, keyboard reachability, and error recovery with actual users. A feature can improve one interaction while leaving other barriers intact.

In a student software project, the relevant workflow begins before the agent session. The team defines the repository, permitted files, data classification, transcript location, and acceptance tests. During the session, students avoid pasting secrets or private records and keep source citations outside transient model commentary. Afterward, they inspect the exact diff, rerun tests, record unresolved limitations, and retain only the transcript evidence required by course or research policy. The source repository remains the authoritative artifact.

Hosted environments deserve special attention because per-session directories can multiply quickly. Administrators should test collision handling, access controls, cleanup, backup scope, and what happens when a session is resumed or moved. A short project label should map to a stable internal identifier. Learners should be told whether transcripts form part of assessment evidence and how to challenge an inaccurate or inappropriate record. Teachers should not use raw transcript length as a proxy for effort or understanding.

For AIEDHK, the release is useful because it makes infrastructure and interface choices visible. Responsible agent use is not only about model output; it includes the records created around that output and the human ability to inspect them. Transcript minimization, clear ownership, accessible controls, and clean-code verification belong in one workflow. Claude Code 2.1.234 can make hosted organization and keyboard use more manageable, but educational trust still rests on privacy rules, reproducible artifacts, and independent review rather than on session metadata. Periodic deletion audits should confirm that expired transcripts actually leave active storage and protected backups according to the published institutional retention schedule. Those audits should also document exceptions, responsible owners, and a dated corrective-action deadline.