# Wegent

Open-source AI-native operating system for defining, organizing, and running intelligent agent teams.

## Agent Decision Summary
- Risk level: low
- Source confidence: high
- Recommended workflows: chatbot
- Permission surface: messages
- Agent JSON: https://www.openagent.bot/bots/wegent.agent.json

## Summary
Wegent is an open-source AI-native operating system for defining, organizing, and running intelligent agent teams. It is relevant to bot and agent-team workflows where multiple assistants, roles, or chat-oriented agents need structure.


## Guide
Wegent is an open-source AI-native operating system for agent teams.

### What it is
It helps define, organize, and run intelligent agents in a team structure.

### Why it matters
The next wave of bots often looks like coordinated agent teams rather than one chatbot.

### How it works
Start with one small team of agents, define roles clearly, and test whether the system improves coordination over a single assistant.


### FAQ
- Is Wegent open source?
  - Yes. The GitHub repository is listed under the Apache-2.0 license.
- Why is Wegent listed under bots?
  - It is not a narrow chatbot; it belongs near bots because it organizes chat-oriented intelligent agent teams.
## What It Does
It helps define, organize, and run intelligent agents in a team structure.

## How To Evaluate
Start with one small team of agents, define roles clearly, and test whether the system improves coordination over a single assistant.

## Why It Matters
Many bot workflows are becoming teams of agents rather than one chatbot. Wegent matters because it focuses on organizing and running agent teams as an operating system layer.


## Best For
- Teams experimenting with multi-agent assistants
- Users organizing AI teammates for chat and work coordination
- Builders comparing agent-team operating systems

## Not For
- Users who only need a single chat widget
- Teams looking for a narrow Telegram or Discord bot

## What It Actually Does
- Agent-team organization: Wegent focuses on defining and organizing intelligent agent teams.
  - Why it matters: Complex assistant workflows often need roles and coordination rather than one generic bot.
- AI-native OS framing: The project describes itself as an AI-native operating system.
  - Why it matters: An OS-style layer can give agent teams a shared structure for work and interaction.
- Chat and agent ecosystem fit: Repository topics include chatbot, ChatGPT, Claude Code, Gemini, and NotebookLM.
  - Why it matters: Wegent sits near the boundary between chatbots, agent teams, and work assistants.

## Typical Use Cases
- Agent team workspace: Define roles and organize multiple agents for recurring workflows.
- AI assistant operations: Run assistants as a structured team rather than isolated chat sessions.
- Bot platform evaluation: Compare Wegent with chatbot frameworks and agent OS projects.

## How It Compares
- When to choose Wegent: Compare it with nearby bots by looking at hosting model, integration surface, license, and whether the official docs show the workflow you need.

## Fit Matrix
- Coding agent workflow: partial. Wegent has at least one signal for coding agent workflow, but should be checked against a real task before adoption. Required check: Run a small repository change and inspect the diff, tests, and rollback path.
- Reusable skill workflow: partial. Wegent has at least one signal for reusable skill workflow, but should be checked against a real task before adoption. Required check: Run one skill end to end and check whether it produces evidence or structured output.
- Browser automation: weak. Wegent is not primarily positioned for browser automation in the current metadata. Required check: Run one non-sensitive website task and inspect clicks, waits, retries, and changed URLs.
- Connector or protocol layer: weak. Wegent is not primarily positioned for connector or protocol layer in the current metadata. Required check: Connect one low-risk service, then inspect schemas, auth scope, errors, and logs.
- Evaluation and observability: weak. Wegent is not primarily positioned for evaluation and observability in the current metadata. Required check: Add one repeatable test case and confirm results can run again in review or CI.
- Local or private AI stack: weak. Wegent is not primarily positioned for local or private ai stack in the current metadata. Required check: Verify hardware requirements, data path, storage, and whether all calls stay in your environment.

## Evidence
- verified: Wegent is listed as open source. Source: License metadata: Apache-2.0
- verified: Wegent has a recorded GitHub repository: wecode-ai/Wegent. Source: Resource facts and GitHub source link.
- inferred: Wegent supports these recorded deployment modes: cloud. Source: OpenAgent decision signal metadata.
- inferred: Wegent is tagged with messaging, chat ui, workflow capabilities. Source: OpenAgent capability taxonomy.

## Missing Checks
- Dedicated docs link is missing.
- Repository freshness has not been recorded.

## Next Actions
- Inspect repository: https://github.com/wecode-ai/Wegent
- Open Homepage: https://wecode-ai.github.io/wegent-docs

## Facts
- Category: bots
- Resource type: bot
- Open source: yes
- License: Apache-2.0
- Last verified: 2026-06-11
- GitHub repo: wecode-ai/Wegent
- GitHub stars: 580

## Capabilities
- messaging
- chat-ui
- workflow

## Structured Use Case Tags
- chatbot

## Getting Started
- Open the GitHub repository: https://github.com/wecode-ai/Wegent
- Read the docs: https://wecode-ai.github.io/wegent-docs

## Links
- GitHub: https://github.com/wecode-ai/Wegent
- Homepage: https://wecode-ai.github.io/wegent-docs

## Structured Outputs
- JSON: https://www.openagent.bot/bots/wegent.json
- Markdown: https://www.openagent.bot/bots/wegent.md
- Agent JSON: https://www.openagent.bot/bots/wegent.agent.json
- Canonical: https://www.openagent.bot/bots/wegent