Openclaw Agents: Difference between revisions
Jump to navigation
Jump to search
(Added Knowledge Graph section) |
(Fix: remove --- horizontal lines (7 removed)) |
||
| Line 18: | Line 18: | ||
* 언제 사용하는가? - 서버 구성, 성능 튜닝, 문제 해결 시 | * 언제 사용하는가? - 서버 구성, 성능 튜닝, 문제 해결 시 | ||
== Purpose == | == Purpose == | ||
| Line 28: | Line 27: | ||
* Non-goals: 다른 주제로의 확장 | * Non-goals: 다른 주제로의 확장 | ||
== Key Concepts == | == Key Concepts == | ||
| Line 42: | Line 40: | ||
|} | |} | ||
== Detailed Explanation == | == Detailed Explanation == | ||
| Line 67: | Line 64: | ||
|We use this agent to setup general purpose bare metal system configuration | |We use this agent to setup general purpose bare metal system configuration | ||
== Best Practices == | == Best Practices == | ||
| Line 75: | Line 71: | ||
* 테스트 환경에서 먼저 검증 | * 테스트 환경에서 먼저 검증 | ||
== References == | == References == | ||
| Line 81: | Line 76: | ||
* [https://wiki.hpcmate.com Openclaw Agents] | * [https://wiki.hpcmate.com Openclaw Agents] | ||
== Related Pages == | == Related Pages == | ||
| Line 90: | Line 84: | ||
* [[Network]] | * [[Network]] | ||
[[Category:AI]] | [[Category:AI]] | ||
Latest revision as of 11:30, 17 July 2026
Overview
Openclaw Agents에 대한 기술 문서입니다.
Summary
- 무엇인가? - Openclaw Agents
- 왜 필요한가? - HPC 및 서버 환경에서 필수 개념
- 언제 사용하는가? - 서버 구성, 성능 튜닝, 문제 해결 시
Purpose
이 문서가 존재하는 이유
- Goal: Openclaw Agents에 대한 기술 정보 제공
- Scope: Openclaw Agents의 개념, 사용법, 설정
- Non-goals: 다른 주제로의 확장
Key Concepts
| Concept | Description | Related |
|---|---|---|
| Openclaw Agents | HPC/서버 환경에서 중요한 기술 개념 | Linux, Server |
Detailed Explanation
| Strategy | Description | Advantages | Best Use Case |
|---|---|---|---|
| Strategy ①: Specialized Individual Agents (Library) | Create separate .md files for each role, such as coder.md, tester.md, or reviewer.md. | Simple to implement and very easy to manage individual roles. | Quick, single-purpose tasks or simple automation. |
| Strategy ②: Orchestrator Pattern (Manager-Worker) | A "Manager" agent analyzes the user's request and uses sessions_spawn to delegate sub-tasks to specific agents. | High autonomy; can handle complex, multi-step reasoning without human intervention. | Complex software development or multi-stage project management. |
| Strategy ③: Pipeline Configuration (Sequential) | A chain of agents where the output of one agent serves as the input for the next (e.g., Scraper -> Analyzer -> Notifier). | Provides a robust, automated workflow for continuous data processing. | Automated monitoring, data extraction, and reporting pipelines. |
| Agent Group | Type | Description | Details |
|---|---|---|---|
| Baremetal System Configuration | Orchestrator | We use this agent to setup general purpose bare metal system configuration
Best Practices
References
Related PagesKnowledge GraphRelated |
- ↑ Generated by HPCMATE local AI