No-Code Agentist
A daily digest of practical AI agent workflows for non-developers. We isolate actionable no-code guides from viral hype. Scored against human-defined standards.
Daily Summary
1 curated | 1 evaluatedToday's focus centers on bridging the gap between technical agent configuration and everyday use, as benjaminshafii announced , a new tool that separates workflow creation from workflow execution by allowing users to leverage existing skills, MCPs, and workflows from developer tools without requiring technical setup.
Today we’re releasing OpenWork Connect. OpenWork started as a free, open-source desktop app. The goal was to make the fully configured agent experience I had in OpenCode available to coworkers who did not want to set up repositories, copy configuration files, or learn a new developer tool. But we tried to put too much into one app. The person building workflows and the person using them often need completely different interfaces. OpenWork Connect separates those two experiences. You can now take the skills, MCPs, and workflows you already use in OpenCode, Codex, Claude Code, Cursor, or OpenWork and share them directly with your coworkers. Assign a workflow to Susan and it appears inside her OpenWork automatically. She does not need to install the skill or copy an MCP configuration. If a service requires her account, she signs in once and continues. The same setup also works in the other direction. Add the OpenWork MCP to Codex, Claude Code, OpenCode, or another compatible agent and you can access the same skills and connections from there too. Your setup is no longer tied to one app, one agent, or one computer. This is live today for OpenWork users. It replaces a lot of copying, manual installation, and forcing everyone on a team to use the same interface. It also changes where OpenWork can go next. The desktop app remains the main surface today, but we are working toward bringing the same workflows to Slack, mobile, and wherever people already communicate and work.