EveryDev.ai
Subscribe
Main Menu
  • Tools
  • Developers
  • Topics
  • Discussions
  • Communities
  • Users
  • News
  • Podcasts
  • Blogs
  • Builds
  • Contests
  • Compare
  • Arena
  • Polls
Rate toolsCreate
AI Tools by Topic
  • AI Coding Assistants
  • Agent Frameworks
  • MCP Servers
  • AI Prompt Tools
  • Vibe Coding Tools
  • AI Design Tools
  • AI Database Tools
  • AI Website Builders
  • AI Testing Tools
  • LLM Evaluations
Follow Us
  • X / Twitter
  • LinkedIn
  • Reddit
  • Discord
  • Threads
  • Bluesky
  • Mastodon
  • YouTube
  • GitHub
  • Instagram
Get Started
  • Users
  • Rate Tools
  • About
  • Editorial Standards
  • Corrections & Disclosures
  • Community Guidelines
  • Advertise
  • Contact Us
  • Newsletter
  • Submit a Tool
  • Start a Discussion
  • Write A Blog
  • Share A Build
  • Terms of Service
  • Privacy Policy
Explore with AI
  • ChatGPT
  • Gemini
  • Claude
  • Grok
  • Perplexity
Agent Experience
  • llms.txt
Theme
With AI, Everyone is a Dev. EveryDev.ai ©
    1. Home
    2. Topics
    3. Agents
    4. Multi-agent Systems
    5. Which parts of your agent workflow would you put in code?

    Which parts of your agent workflow would you put in code?

    Nolan Carrow's avatarNC
    Nolan Carrow
    October 7, 2026
    0

    Copilot’s Dynamic Workflows let you write the steps in code and leave the reasoning to agents. That seems useful for things like “run the tests before asking for review.” Where would you draw the line? I’d want the program to decide when a change can move forward, but leave room for the agent to figure out how to fix it.

    Tagged inGitHub Copilot·#Multi-agent Systems

    Comments

    Checking profile…