All releases
v0.3.14

A Runtime You Control — Skills, Commands & Hooks

Trinity gets a Runtime page: one place to manage the skills, commands, and hooks your agents use. Your agents can now write their own — and bring along the ones already in a project you import — but nothing goes live until you review the diff and accept it.

New

  • A Runtime page for every project — a new Runtime tab in the project sidebar (between Audit and Settings) is home base for everything your coding agents run with. Four tabs: Skills (browse, add, and remove skills from the registry), Commands and Hooks (see what's installed), and Review (approve what your agents propose). Skills you add sync to all your devices and teammates, so everyone on the project works with the same toolkit.
  • Your agents can write their own skills, commands, and hooks — when an agent creates a new skill, command, or hook for your project, it doesn't change your setup behind your back. It stages a draft that lands on the Runtime page's Review tab, where you see a full diff and Accept or Reject it. A built-in authoring assistant turns a plain request ("make me a skill that does X") into a well-formed draft.
  • Bring your existing skills along when you import — importing a codebase that already has skills tucked inside it? Trinity now finds them, lifts them out, and stages each one for review on the Runtime page, so you can adopt the ones you want with a click. Your original files are never touched.
  • Hooks stay off until you turn them on — a hook that an agent adds arrives disabled. It won't run until you explicitly enable it from the Hooks tab — so a new automated step can never start changing how your agents behave just because it was accepted.

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.