The ultimate harness for coding agents and beyond. All your agents. All your machines. One command center. Start with code, then follow your curiosity and build across disciplines: CAD, circuits, robots, games and music.
TypeScript 3d-modelingagent-frameworkagent-harnessai-agentscadclaude-codecodexcoding-agentsdeveloper-toolsesp32game-developmentmcp-servermulti-agentopen-hardwareopencodeopenharnesspcbroboticsterminaltmux
import 'package:flutter/foundation.dart';
/// Whether this build shows its developer surfaces: Settings ▸ Debug, its ⌘D
/// shortcut, and the in-memory buffer that feeds it (`logStream`).
///
/// A debug build has it; a release build does not. The log *files* are written
/// either way — a shipped app that has no stderr anyone reads is exactly the
/// one whose logs matter (see `logging/app_log.dart`) — but the screen that
/// reads them back is developer furniture, and the ring buffer behind it is
/// memory a user's session should not spend.
///
/// `HARNESS_DEBUG_SURFACE=true` turns it on in a release build, for the one
/// case that is otherwise unreachable: reproducing a fault on a packaged app,
/// where a debug build's timing is not the timing being complained about.
const bool kDebugSurfaceEnabled =
kDebugMode || bool.fromEnvironment('HARNESS_DEBUG_SURFACE');