Profiles and Config: Let One Agent Have Many Homes

Use profiles to separate personal, classroom, local, and production agent behavior without rewriting the app.

19 min · Reviewed 2026

What the local Hermes build teaches

This build lab focuses on the configuration layer that lets one codebase behave like several safe agents. The goal is not to copy a private machine setup. The goal is to learn the architecture pattern well enough to build a small, classroom-safe version.

Profiles give each agent home its own config, memory, tools, model defaults, and delivery settings.

Hermes pattern	Student build	Risk to handle
Name the boundary	a profile matrix that compares demo, classroom, local-private, and production profiles	accidentally sharing memory, tokens, tools, or delivery channels between users or environments
Keep the interface small	Start with one happy path and one failure path	Avoid a demo that only works when everything is perfect
Make the system observable	Log decisions, status, and errors in plain language	Do not log private data or secrets

Build the small version

Draw or write a profile matrix that compares demo, classroom, local-private, and production profiles.
Mark which parts are user-facing, which parts are internal, and which parts require approval.
Choose one low-risk workflow and implement only that workflow first.
Add one failure case before adding a second feature.
Write a short operator note: what the agent may do, what it must ask about, and what it must never do.

profiles:
  demo:
    home: ./profiles/demo
    model: mock-fast
    tools: [calculator, lesson_search]
    delivery: none

  local_private:
    home: ~/.agent/private
    model: local-hermes
    tools: [filesystem_read]
    delivery: desktop

  production:
    home: /app/agent-home
    model: routed
    tools: [approved_actions]
    delivery: emailA classroom-safe skeleton inspired by the local Hermes architecture scan.

The big idea: profile is not decoration. It is part of the product architecture students need before an agent becomes safe enough to use with real people.

End-of-lesson check

15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-hermes-profile-config-layer-creators

What is the core idea behind "Profiles and Config: Let One Agent Have Many Homes"?
1. Use profiles to separate personal, classroom, local, and production agent behavior without rewriting the app.
2. Hermes
3. per-task win rate
4. Pin a specific model id, not a 'latest' alias — your behavior will change withou…
Which term best describes a foundational idea in "Profiles and Config: Let One Agent Have Many Homes"?
1. home directory
2. profile
3. environment isolation
4. config resolver
A learner studying Profiles and Config: Let One Agent Have Many Homes would need to understand which concept?
1. profile
2. environment isolation
3. home directory
4. config resolver
Which of these is directly relevant to Profiles and Config: Let One Agent Have Many Homes?
1. profile
2. home directory
3. config resolver
4. environment isolation
Which of the following is a key point about Profiles and Config: Let One Agent Have Many Homes?
1. Draw or write a profile matrix that compares demo, classroom, local-private, and production profiles.
2. Mark which parts are user-facing, which parts are internal, and which parts require approval.
3. Choose one low-risk workflow and implement only that workflow first.
4. Add one failure case before adding a second feature.
Which of these does NOT belong in a discussion of Profiles and Config: Let One Agent Have Many Homes?
1. Mark which parts are user-facing, which parts are internal, and which parts require approval.
2. Hermes
3. Choose one low-risk workflow and implement only that workflow first.
4. Draw or write a profile matrix that compares demo, classroom, local-private, and production profiles.
What is the key insight about "From the local Hermes scan" in the context of Profiles and Config: Let One Agent Have Many Homes?
1. Hermes
2. per-task win rate
3. Hermes supports profile-style home directories so an operator can switch where the agent reads config and stores state.
4. Pin a specific model id, not a 'latest' alias — your behavior will change withou…
What is the key insight about "Safety pitfall" in the context of Profiles and Config: Let One Agent Have Many Homes?
1. Hermes
2. per-task win rate
3. Pin a specific model id, not a 'latest' alias — your behavior will change withou…
4. Accidentally sharing memory, tokens, tools, or delivery channels between users or environments.
What is the key warning about "Scope your agents tightly" in the context of Profiles and Config: Let One Agent Have Many Homes?
1. Always define: goal, tools, permissions, and stop condition before executing.
2. Hermes
3. per-task win rate
4. Pin a specific model id, not a 'latest' alias — your behavior will change withou…
Which statement accurately describes an aspect of Profiles and Config: Let One Agent Have Many Homes?
1. Hermes
2. This build lab focuses on the configuration layer that lets one codebase behave like several safe agents.
3. per-task win rate
4. Pin a specific model id, not a 'latest' alias — your behavior will change withou…
What does working with Profiles and Config: Let One Agent Have Many Homes typically involve?
1. Hermes
2. per-task win rate
3. Profiles give each agent home its own config, memory, tools, model defaults, and delivery settings.
4. Pin a specific model id, not a 'latest' alias — your behavior will change withou…
Which of the following is true about Profiles and Config: Let One Agent Have Many Homes?
1. Hermes
2. per-task win rate
3. Pin a specific model id, not a 'latest' alias — your behavior will change withou…
4. The big idea: profile is not decoration. It is part of the product architecture students need before an agent becomes safe enough to use wit…
Which best describes the scope of "Profiles and Config: Let One Agent Have Many Homes"?
1. It focuses on Use profiles to separate personal, classroom, local, and production agent behavior without rewriting
2. It is unrelated to agentic workflows
3. It applies only to the opposite beginner tier
4. It was deprecated in 2024 and no longer relevant
Which section heading best belongs in a lesson about Profiles and Config: Let One Agent Have Many Homes?
1. Hermes
2. Build the small version
3. per-task win rate
4. Pin a specific model id, not a 'latest' alias — your behavior will change withou…
Which of the following is a concept covered in Profiles and Config: Let One Agent Have Many Homes?
1. home directory
2. environment isolation
3. profile
4. config resolver

← Back to interactive lesson

Tendril · Creators · Agentic AI

Profiles and Config: Let One Agent Have Many Homes

Use profiles to separate personal, classroom, local, and production agent behavior without rewriting the app.

19 min · Reviewed 2026

What the local Hermes build teaches

Profiles give each agent home its own config, memory, tools, model defaults, and delivery settings.

Hermes pattern	Student build	Risk to handle
Name the boundary	a profile matrix that compares demo, classroom, local-private, and production profiles	accidentally sharing memory, tokens, tools, or delivery channels between users or environments
Keep the interface small	Start with one happy path and one failure path	Avoid a demo that only works when everything is perfect
Make the system observable	Log decisions, status, and errors in plain language	Do not log private data or secrets

Build the small version

Draw or write a profile matrix that compares demo, classroom, local-private, and production profiles.
Mark which parts are user-facing, which parts are internal, and which parts require approval.
Choose one low-risk workflow and implement only that workflow first.
Add one failure case before adding a second feature.
Write a short operator note: what the agent may do, what it must ask about, and what it must never do.

profiles:
  demo:
    home: ./profiles/demo
    model: mock-fast
    tools: [calculator, lesson_search]
    delivery: none

  local_private:
    home: ~/.agent/private
    model: local-hermes
    tools: [filesystem_read]
    delivery: desktop

  production:
    home: /app/agent-home
    model: routed
    tools: [approved_actions]
    delivery: emailA classroom-safe skeleton inspired by the local Hermes architecture scan.

The big idea: profile is not decoration. It is part of the product architecture students need before an agent becomes safe enough to use with real people.

End-of-lesson check

15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-hermes-profile-config-layer-creators

What is the core idea behind "Profiles and Config: Let One Agent Have Many Homes"?
1. Use profiles to separate personal, classroom, local, and production agent behavior without rewriting the app.
2. Hermes
3. per-task win rate
4. Pin a specific model id, not a 'latest' alias — your behavior will change withou…
Which term best describes a foundational idea in "Profiles and Config: Let One Agent Have Many Homes"?
1. home directory
2. profile
3. environment isolation
4. config resolver
A learner studying Profiles and Config: Let One Agent Have Many Homes would need to understand which concept?
1. profile
2. environment isolation
3. home directory
4. config resolver
Which of these is directly relevant to Profiles and Config: Let One Agent Have Many Homes?
1. profile
2. home directory
3. config resolver
4. environment isolation
Which of the following is a key point about Profiles and Config: Let One Agent Have Many Homes?
1. Draw or write a profile matrix that compares demo, classroom, local-private, and production profiles.
2. Mark which parts are user-facing, which parts are internal, and which parts require approval.
3. Choose one low-risk workflow and implement only that workflow first.
4. Add one failure case before adding a second feature.
Which of these does NOT belong in a discussion of Profiles and Config: Let One Agent Have Many Homes?
1. Mark which parts are user-facing, which parts are internal, and which parts require approval.
2. Hermes
3. Choose one low-risk workflow and implement only that workflow first.
4. Draw or write a profile matrix that compares demo, classroom, local-private, and production profiles.
What is the key insight about "From the local Hermes scan" in the context of Profiles and Config: Let One Agent Have Many Homes?
1. Hermes
2. per-task win rate
3. Hermes supports profile-style home directories so an operator can switch where the agent reads config and stores state.
4. Pin a specific model id, not a 'latest' alias — your behavior will change withou…
What is the key insight about "Safety pitfall" in the context of Profiles and Config: Let One Agent Have Many Homes?
1. Hermes
2. per-task win rate
3. Pin a specific model id, not a 'latest' alias — your behavior will change withou…
4. Accidentally sharing memory, tokens, tools, or delivery channels between users or environments.
What is the key warning about "Scope your agents tightly" in the context of Profiles and Config: Let One Agent Have Many Homes?
1. Always define: goal, tools, permissions, and stop condition before executing.
2. Hermes
3. per-task win rate
4. Pin a specific model id, not a 'latest' alias — your behavior will change withou…
Which statement accurately describes an aspect of Profiles and Config: Let One Agent Have Many Homes?
1. Hermes
2. This build lab focuses on the configuration layer that lets one codebase behave like several safe agents.
3. per-task win rate
4. Pin a specific model id, not a 'latest' alias — your behavior will change withou…
What does working with Profiles and Config: Let One Agent Have Many Homes typically involve?
1. Hermes
2. per-task win rate
3. Profiles give each agent home its own config, memory, tools, model defaults, and delivery settings.
4. Pin a specific model id, not a 'latest' alias — your behavior will change withou…
Which of the following is true about Profiles and Config: Let One Agent Have Many Homes?
1. Hermes
2. per-task win rate
3. Pin a specific model id, not a 'latest' alias — your behavior will change withou…
4. The big idea: profile is not decoration. It is part of the product architecture students need before an agent becomes safe enough to use wit…
Which best describes the scope of "Profiles and Config: Let One Agent Have Many Homes"?
1. It focuses on Use profiles to separate personal, classroom, local, and production agent behavior without rewriting
2. It is unrelated to agentic workflows
3. It applies only to the opposite beginner tier
4. It was deprecated in 2024 and no longer relevant
Which section heading best belongs in a lesson about Profiles and Config: Let One Agent Have Many Homes?
1. Hermes
2. Build the small version
3. per-task win rate
4. Pin a specific model id, not a 'latest' alias — your behavior will change withou…
Which of the following is a concept covered in Profiles and Config: Let One Agent Have Many Homes?
1. home directory
2. environment isolation
3. profile
4. config resolver

← Back to interactive lesson