CoreSpeed

the "credentials held by CoreSpeed, never handed to your agents" line is the part that actually matters to me, that's the difference between a tool and a liability. we've been wrestling with a similar split at Dial on the data side - wanting the agent to act on behalf of the business without the agent (or us) ever seeing the raw credential. question on Smart Approval: when an agent hits an action that needs OK mid-task, does it block and wait, or queue the rest of the plan and come back to that one step once you approve

Multiple accounts per app is the detail I like Personal and company X accounts side by side, and the agent picks the right one. I always end up logging in and out for that.

keeping the app credentials away from agents makes sense. if a smart approval rule is ambiguous, does the action wait for me or go through?

How does an agent choose among the available media-generation tools? Can the user specify a preferred provider?

Connecting an app once and reusing the same accounts and memory across Claude Code, Codex and Cursor solves a real annoyance, since everyone ends up wiring the same integrations over and over. Supporting multiple accounts per app is a thoughtful detail. How do you keep shared versus private memory separated between agents?

Is there a way to give an agent access to only a small subset of connected apps?

Can sensitive fields be excluded from activity logs? I'm curious how you balance troubleshooting detail with privacy.

The activity log seems like a useful place to start a demo. It could show what the agent accessed, changed, and spent.

The activity logs caught my attention more than the one MCP part. Once agents start doing more things on their own being able to see what actually happened becomes pretty important. How detailed are the logs?

Wait this actually solves one of my biggest annoyances with coding agents lol. Every time I try a new one I end up reconnecting and configuring everything all over again. The “set it up once” idea makes so much sense.

Been testing it. Changed my life fr.

How does Smart Approval work when an agent wants to perform a sensitive action? Can users approve each request individually?

Hey Product Hunt! 👋 We're the founding team of CoreSpeed.We kept hitting the same wall: our agents were capable, but getting them to do real work meant wiring up integrations, managing credentials, and rebuilding context. After rebuilding that foundation across three products, we realized the foundation itself was the product.So we're building CoreSpeed, an operating system for agents. Set it up once, and every MCP agent you sign in, whether Claude Code, Codex, Cursor or your own, works from the same setup:- Your connected apps, with multiple accounts per app, like personal and company accounts on X- Saved memory, shared with your team or kept private- Built-in web search, social research, and image, audio and video generation. Think of this layer as OpenRouter for agent tools: no separate API keys or provider subscriptions. Just pay as you go through CoreSpeed.- App credentials held by CoreSpeed, never handed to your agents- Budgets, activity logs and Smart Approval (beta), where you write in plain English which actions need your OK firstPlanned, not live yet: Agent Drive, Mail, Pay, sandboxes, and more.Everything your agents need, through one MCP endpoint. Give this to your agent to start for free:set up https://corespeed.io/SKILL.md