How to share Agentic Workflows in the cloud?

TL;DR

The video presents three quick ways to share Agentic Workflows in the cloud: using GitHub Codespaces with a one click invite, duplicating the directives and executions folders into a new workspace, or distributing via a traditional GitHub repo. Each method automates setup and runs on cloud infrastructure, with costs kept low by on demand usage and hosting that spins down when inactive.

Transcript

So, let's say you have a bunch of Agentic workflows running for you, maybe even in parallel, doing really productive things like scraping leads, enriching them, adding them to a database, or updating your CRM. If you guys don't know how that works, watch my recent video for a full end to-end walkthrough on Agentic Workflows. Now, once you've determ... Read More

Key Insights

• Agentic Workflows are designed to be portable between local and cloud environments, enabling teams to collaborate without duplicating manual setup steps. The cloud deployment approach reduces friction by providing shared, ready to run environments for collaborators.
• A GitHub Codespaces based method offers a one click setup that creates a hosted VS Code instance, configures authentication, and preinstalls dependencies, making it the simplest sharing option for non-technical users.
• Duplicating directives and executions across a new workspace allows the exact same automation logic to run in a different environment, provided the new workspace is prepared with the same file structure and a matching runtime environment.
• Traditional GitHub repos are a zero cost option when using a collaborator's own infrastructure, but require more technical steps and familiarity with Git workflows, potentially raising the barrier for some users.
• The workflow description emphasizes a lightweight sharing prompt and explicit scaffolding to adapt complex agentic systems for new users, helping ensure clear expectations about what will run and what needs to be configured.
• Inviting collaborators is designed to be straightforward via GitHub usernames, with invites generating access links and a guided process to connect remote workspaces, enabling quick onboarding.
• Security considerations appear in passing, with a suggestion that users can avoid committing certain sensitive artifacts to repos and instead share step by step instructions, though the video itself demonstrates direct repo commits in some cases.
• The cost model presented centers on hosted servers like Codespaces costing around eighteen cents per hour with automatic spin down, making cloud sharing affordable for intermittent use.
• More videos from this channel:
  • How AI Agencies Sign Clients: Real Wins From 1000+ Owners
  • How to land your first AI client using social proof
  • How to Reduce Fable 5 API Costs With Images
• More from this channel: Nick Saraev

Questions & Answers

Q: How can I share Agentic Workflows with teammates using Codespaces?

Codespaces provides a one click setup that creates a hosted VS Code instance inside a GitHub container, including authentication, directives, scripts, and requirements. After inviting collaborators by GitHub username, the remote workspace is configured in the browser, reducing local setup and enabling collaborators to run the agentic workflows in the cloud. The process includes connecting to a chosen agent and logging into the cloud code service to start interactive sessions, giving teams a fast start without managing local environments.

Q: What is the simplest way to duplicate an Agentic setup for another workspace?

The simplest approach is to duplicate the directives and executions folders from the original workspace into a new workspace, then supply a share prompt that tells the model to use the given framework and accompanying scripts. This method creates a near identical runtime environment in the new workspace and allows the new user to execute the same agents with the same configurations and dependencies, minimizing manual reconfiguration.

Q: How does using a traditional GitHub repo differ from Codespaces for sharing?

Using a traditional GitHub repo relies on the recipient using their own infra and GitHub account, which can reduce hosting costs but increases setup complexity. It requires the user to clone or pull the repository, configure environment variables or credentials, and ensure dependencies are installed. This method is zero cost if run on the user’s own infrastructure, but it demands more technical familiarity from the collaborator.

Q: What role do prompts play in sharing agentic workflows?

Prompts accompany the shared scripts to instruct collaborators on how to instantiate and run the workflows in their environment. They guide the model in setting up necessary configurations, installing dependencies, and initializing the agent with appropriate constraints. Clear prompts help ensure consistent behavior across different users and environments, reducing misconfigurations and miscommunications.

Q: What costs should I expect when sharing via Codespaces?

Codespaces runs on a hosted server that costs about eighteen cents an hour, but the server spins down when not in use, so the actual ongoing cost is typically lower for users who do not run the agentic workflows continuously. This makes cloud sharing affordable for occasional or project-based use while avoiding constant hosting expenses.

Q: How do I invite a collaborator to a Codespaces workspace?

To invite a collaborator, you generate an invitation by their GitHub username, and the recipient receives an email link to accept the invite. Once accepted, the collaborator gains access to the workspace and can connect to the agent flow in the cloud. This process centralizes permissions through GitHub and keeps collaboration streamlined.

Q: What should I consider about security when sharing agentic workflows?

Security considerations include decisions about whether to commit sensitive tokens or configuration files to the repository. The video notes that users can avoid committing these items and instead provide step-by-step setup instructions, which can reduce exposure. When sharing with organizations, assess risk tolerance and consider using more isolated or tokenized configurations to protect credentials.

Q: What are the key steps to set up a new cloud workspace from scratch?

Create a new folder structure with directives and executions, move or paste the relevant files into their respective folders, and include the shared agentic workflow document. Then generate the environment setup prompts and install dependencies via a requirements.txt. Finally, validate the workspace by connecting to the chosen agent and confirming the workflow runs as intended, ensuring the cloud environment mirrors the original setup.

Summary & Key Takeaways

• The video shows three practical ways to move Agentic Workflows to the cloud, emphasizing ease of setup and collaboration. It covers GitHub Codespaces, direct folder replication, and GitHub repos, with notes on cost and security considerations. The approach aims to minimize manual configuration for teammates.

• It highlights that cloud deployments can be shared with collaborators through simple prompts and scaffolding, while cautioning about potential security choices such as whether to commit tokens or sensitive files to repositories. Practical steps are demonstrated end to end.

• The speaker walks through setting up a cloud environment, creating required folders, and wiring in directives, executions, and agents. It ends with guidance on inviting collaborators and verifying access, aiming to make cloud sharing accessible for non-experts.