# Decide where people guide the work—and where agents can proceed.

Human-in-the-loop and no-human-in-the-loop describe two operating approaches. In practice, a workflow can combine human decisions with agent-led steps, according to the work and the controls the product supports.

Canonical: https://www.magicstride.in/docs/human-in-the-loop

MagicStride — AI for the way your organization works.

## People guide key decisions.

Use this approach when a person should review a plan, decide on a consequential action, or approve a result before it moves on. Agents can prepare work; responsibility for the decision stays with the designated person. Technically, this is the human-in-the-loop operating model.

## Agents work within defined limits.

Use this approach for work that can proceed under boundaries established in advance: the allowed scope, resources, and actions are set before the work begins. Technically, this is the no-human-in-the-loop operating model.

## Combine the approaches.

Many workflows need both: agents carry out defined steps while people guide decisions, review exceptions, or approve a hand-off. Set the division of responsibility around the work — not around the tool.

## Make exceptions explicit.

Decide what happens when the workflow reaches something outside its agreed scope: stop, hand off to a person, or follow another approved path. The exception plan is part of the workflow design.

## Questions and answers

### Does no-human-in-the-loop mean no governance?

No. It means the workflow does not pause for a person at every step. Its permitted scope and actions are still defined by the organization, within the controls the product supports.

### Can we combine both approaches in one workflow?

Yes — a workflow can mix human decisions with agent-led steps. How that mix is configured is confirmed against current product capabilities during design.

### Who decides which steps need review?

The organization and the workflow owner decide, with MagicStride helping design and implement the responsibilities.

## Explore further

- [Home](https://www.magicstride.in/)

- [Platform](https://www.magicstride.in/platform)

- [Architecture](https://www.magicstride.in/architecture)

- [Enterprises](https://www.magicstride.in/solutions/enterprise)

- [Teams](https://www.magicstride.in/solutions/teams)

- [Engineering](https://www.magicstride.in/solutions/engineering)

- [Business operations](https://www.magicstride.in/solutions/business)

- [Finance & operations](https://www.magicstride.in/solutions/finance-operations)

- [Customer support](https://www.magicstride.in/solutions/customer-support)

- [Sales & go-to-market](https://www.magicstride.in/solutions/sales)

- [Research & knowledge](https://www.magicstride.in/solutions/research-knowledge)

- [People operations](https://www.magicstride.in/solutions/people-operations)

- [Developers](https://www.magicstride.in/developers)

- [Documentation](https://www.magicstride.in/docs)

- [Core concepts](https://www.magicstride.in/docs/concepts)

- [Workflow lifecycle](https://www.magicstride.in/docs/workspace-lifecycle)

- [Roadmap](https://www.magicstride.in/roadmap)

- [About](https://www.magicstride.in/about)

- [Pricing](https://www.magicstride.in/pricing)

- [Blog](https://www.magicstride.in/blog)

- [Announcing MagicStride](https://www.magicstride.in/blog/announcing-magicstride)