Issues
Skip to article

Your ThisDamnThing workspace

Run the setup examples from a parent directory outside your projects and the ThisDamnThing source checkout. Paths are relative to that directory.

ThisDamnThing keeps reviewed knowledge in local Markdown and links projects at their existing paths. Claude or Codex supplies the active agent; optional stacks add workflows. A new workspace has zero stacks and zero registered projects.

Use skills in your agent for everyday work. These guides show Claude's /tdt-* names; in Codex use the same name with $ or the skill picker. The agent runs the underlying commands for you. Terminal examples are secondary instructions for technical users. Setup and some maintenance operations have no dedicated skill; you can ask your agent to carry them out.

Start with getting started, then use these guides:

brain/ holds knowledge; .tdt/ holds skills, configuration and working state; docs/ holds these guides. Provider instructions and skill bridges point into .tdt/. Keep the workspace outside the ThisDamnThing source repository and keep your external projects at their original locations.

Use /tdt-workspace to inspect the workspace and explain diagnostics. For a terminal check, run tdt doctor from the workspace or a subdirectory. Elsewhere, use tdt --workspace "./my workspace" doctor. A healthy file layout does not prove that your host has trusted or executed its hooks.

Initialization preserves unrelated files and refuses ownership conflicts and managed-path symlinks. Ask your agent to refresh core resources after an upgrade. For technical users, repeat tdt init to update unchanged owned core resources and guides; it does not repair arbitrary missing or edited files. Back up your workspace before upgrades and see recovery.