A Runtime You Control — Skills, Commands & Hooks

New

• A Runtime for every project

  home base for everything your coding agents run with: the Skills they can use (browse, add, and remove from the registry), the slash Commands they can call, the Hooks that fire around their work, and a Stage config for tuning which skills each step of a run reaches for. It appears once your project is set up, and what you add syncs to all your devices and teammates, so everyone on the project works with the same toolkit.
• Create skills, commands, and hooks just by describing them

  tell Trinity what you want ("a skill that writes our release notes", "a hook that blocks committing secrets") and an agent drafts it for you, right inside a Runtime conversation. Nothing changes your setup behind your back: the draft opens in a side panel with a full diff to Accept or Reject. Bring an idea, get a well-formed skill.
• Manage your commands and hooks — including when a hook runs

  enable or disable any hook, set exactly which events and tools it fires on, edit it, or remove it; manage your commands the same way. No more read-only lists — the Runtime is something you actually drive.
• Choose which skills each step of a run uses

  the Stage config maps your skills onto the stages of a run — analysis, implementation, audit, documentation — so each agent reaches for the right tools at the right moment instead of every agent seeing everything.
• Hooks stay off until you turn them on

  a new hook arrives disabled. It won't run until you explicitly enable it — so an automated step can never start changing how your agents behave just because it was accepted.
• Bring your existing skills along when you import

  importing a codebase that already has skills tucked inside it? Trinity finds them, lifts them out, and stages each one for review, so you can adopt the ones you want with a click. Your original files are never touched.

Improved

• Review pull requests without leaving Trinity

  the PR Review gate now shows each pull request's diff inline, right next to the Approve / Feedback / Skip buttons. You can read exactly what changed before you approve, instead of opening the PR in a browser.
• See what a story shipped, on the story page

  once a story is merged, its detail view gains a collapsible Changes section with the full merged diff rendered inline — one panel per repository — so you can review the work in context without opening the code viewer.