Changelog Update

Triggers Now Run Inside Pods

🎯 What is it?

When a trigger fires, the conversation it creates now lives directly inside the Pod you've selected. This means every automated run lands in the right workspace context from the start, rather than sitting outside your team's organized spaces.

💡 Why is it useful?

Automated work can quickly become hard to track when it's scattered outside your team's normal environment. By routing triggered conversations into a Pod, everything stays organized, easy to find, and shareable with the right people — automatically placed where the relevant context already lives.

⚙️ How does it work?

When you set up a trigger, you select the Pod where its conversations should run. From then on, each time the trigger fires, the resulting conversation is created inside that Pod alongside your team's related work.

✨ Concrete Use Cases

Here's how you could use it:

• Recurring reporting: A daily trigger that generates a summary now posts its conversation straight into your team's reporting Pod, where everyone already looks for updates.

• Automated monitoring: A trigger watching for specific events creates its conversations inside the dedicated project Pod, so the whole team can review and act on them in context.

📈 Benefits for you

Less time spent hunting for automated runs, better visibility for your team, and cleaner organization of all triggered work — each conversation lands exactly where it belongs, with the right people able to access it.

🚀 How to access it?

This is available to all users. Simply open your trigger configuration and select the Pod where you'd like the triggered conversations to run.