Launched this week
Turn coding agents into teammates anyone can use from Slack, Linear, CLI, API or your browser. Ship features, query data, build dashboards, automate workflows. All within your company's context, skills, integrations, and security guardrails.
the company context and skills layer is the part that differentiates this from just wrapping an API but it's also the part that takes the most setup to be useful. how long does it actually take to get Runtime to the point where it knows enough about your stack, your data schema, your workflows to give useful output rather than generic responses? that onboarding investment is usually what kills team AI tool adoption before it starts
Runtime
@ansari_adin the "how long until it's useful" question is real. In practice, most teams get something useful in the first session because you bring your own secrets and integrations from the start. The skills layer deepens over time, but you're not blocked on it to get value on day one.
Embedding actual code execution inside Slack is a much bigger deal than it sounds, most "AI in Slack" tools just generate text and call it a day. The sandboxed environment is what makes this viable for teams, since nobody wants an agent touching production. Curious about long-running tasks though; if a test suite takes 8 minutes to run, does Slack handle that without the bot timing out?
Runtime
@ayushi18 Great catch! Runtime agents run fully in the background, they don't block the Slack thread while working. You get a notification when they're done, so an 8-minute test suite is totally fine.
As a small bootstrapped company building a product that has many dependencies and environments, we found that over time, each engineer became very siloed on the part of the stack that they could work on because setting up the right dev environment on another computer took forever.
Runtime solves this issue for us and now every engineer can contribute pretty effortlessly at any part of the stack at a moments notice. Pretty game changing stuff going on here.
Runtime
@sebastian_fay1 thanks Sebastian! We're glad Runtime has been of help to your business.
Used Runtime as soon as it launched and it was super useful to get non-technical folks setup and contribute code to a mature codebase while having the right guardrails in place.
Runtime
@oscar_oliva glad Runtime has been of help! Thanks for the early feedback.
Sandboxed coding agents sound intriguing. How do they handle permission issues when running scripts on a shared server? Seems like a neat way to let everyone experiment safely.
Runtime
@andrewbuilds Each agent runs in its own isolated sandbox snapshotted from a pre-configured template, so there's no bleed between users. Secrets go through an encrypted vault and proxy, agents never see raw credentials. Admins can also set egress allowlists, command-level gates, and spend caps, so experimentation stays safe without anyone stepping on each other.
In conclusion: Runtime avoids the shared server problem entirely. Each agent runs in its own isolated sandbox, so there's no permission collision between users.
Good job guys, I think it should be clearer how the whole flow works and if at any point you guys have access to our repos and if so how do you manage it, I understand it's sandboxed and you delete the filesystem afterwards but it's not entirely clear if you have access somehow so that made me hesitate to use it
Runtime
@jose_cyc thanks for the feedback! How do you think we can clarify it? Would SOC2 compliant give you that trust you need to try us?
Really like the sandboxed approach here. Giving coding agents isolated environments feels much safer and more scalable for teams than shared setups. Curious how you manage resource limits for long-running agent workflows.