agentos
Provides Telegram Business onboarding support, including generating a setup plan and guiding the authorization and connection of a personal Telegram account as a business interface.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@agentosrun a health check"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Crystal AgentOS
A free, local-first control plane for personal AI agents.
Crystal AgentOS helps you turn an AI client into a governed working environment: local configuration, bounded task briefs, MCP tools, health checks and a clear Telegram Business onboarding path.
The community edition is intentionally small. It contains no vendor account, private host, production credential or hidden cloud dependency.
Latest release
v0.4.0 adds Full Inventory and an AgentOS-native two-day public update advisory. It also includes deterministic model routing, evidence-based completion and the owner-only Telegram Session Hub.
Read the release notes, visit the project website or open an issue with a bug, question or blunt technical review.
Related MCP server: Mobile MCP Command Bridge
Why AgentOS?
An AI model can reason, but a dependable agent also needs boundaries:
where configuration and secrets live;
which actions are allowed;
how a task is classified before execution;
how tools are exposed to ChatGPT and other MCP clients;
how a personal Telegram account becomes an authorized business interface;
how a result can be checked and rolled back.
AgentOS provides that control layer without taking ownership of your data.
Governed model routing
Version 0.3 adds a deterministic routing plan for Codex tasks:
Sol/high coordinates the root task and difficult reviews;
Terra/medium handles bounded implementation and investigation;
Luna/low handles narrow classification, extraction and routing;
Astra/high is reserved for explicitly critical root work.
agentos route-task --mode implementation --role root
agentos route-task --mode classification --role worker --complexity lowThe command returns an exact model and reasoning effort. It does not claim
that a model ran. Codex delegates in supported clients after a direct request or
an applicable project/skill instruction; runtime activity still needs separate
proof. The default is delegate_by_default=false.
Truthful completion gate
A completed thread or successful command is not sufficient evidence that a
product outcome works. agentos assess-result --file evidence.json requires
current PASS evidence for every acceptance criterion. Missing, stale,
future-dated, failed or historically bound evidence blocks COMPLETE, and a
newer failure supersedes an older PASS. See Result evidence.
Full Inventory
Register the project roots you want AgentOS to know. The collector emits only paths, knowledge classes, sizes and SHA-256 identities; it never copies file contents and never auto-loads history.
agentos inventory collect --catalog /absolute/path/projects.json --output ~/.agent-os/state/inventory.json
agentos inventory select --input ~/.agent-os/state/inventory.json --project-id my-projectThe six classes are project, roadmap, skill, problem, host and
history. See Full Inventory.
Update advisory
Every AgentOS command checks the local advisory state. If 48 hours have elapsed, AgentOS reads the official public GitHub tags and records whether a newer Community Edition exists. It stays quiet while current, retries an unavailable check after six hours and never installs anything automatically.
agentos update-check
agentos update-check --forceThis is activity-driven, not a background daemon: if AgentOS is idle, the check runs on the next command. Public tag metadata is informational and cannot authorize software or host mutation. See Update checks.
Install
Requires Python 3.11 or newer.
python3 -m venv .venv
. .venv/bin/activate
pip install .
agentos init
agentos doctorFor development:
pip install -e '.[dev]'
pytest
ruff check .Telegram Business onboarding
AgentOS uses a Telegram-first sequence:
Create an account in the official Telegram application if you do not have one.
Request approval from your AgentOS owner or administrator.
Authorize a
StringSessionusing Telegram QR.Store the explicitly approved
API_ID,API_HASH,STRING_SESSIONbundle locally.Connect Telegram Business and its business bot.
Add AgentOS to an MCP-compatible client.
Run a harmless end-to-end verification task.
No website is required by this flow. Credentials must never be pasted into an AI conversation, issue, log or repository.
Print the machine-readable plan:
agentos telegram-planMCP
Generate a client configuration template:
agentos mcp-configThe included stdio server exposes three safe starter tools:
agentos_get_telegram_setup_planagentos_normalize_taskagentos_doctor
It does not expose arbitrary shell, SSH, file reads or stored credentials.
Telegram Session Hub
Version 0.2 adds an owner-only local Telegram control surface for Codex:
discover recent persisted sessions from the platform default or configured folders;
inspect GNU Screen sessions on Linux and macOS and show their mapped Codex UUID;
select an existing session and send its next task;
create a new persisted Codex session or a new GNU Screen attached to one;
receive documents and media into a private local inbox;
transcribe voice with local Whisper or an optional OpenAI transcription provider.
GNU Screen is not available on Windows; ordinary Codex session discovery and creation remain supported there. The bot is disabled until an explicit owner ID allowlist and a token environment variable are configured.
agentos sessions
agentos screens
agentos session-capabilities
agentos telegram-botSee Telegram Session Hub for configuration and the exact security/proof model.
Status
0.4.0 is an alpha community release. It is suitable for evaluation and local
development. Production connectors must add their own authentication, durable
receipts, least-privilege runtime and rollback policy.
Community
AgentOS is free software under Apache License 2.0. Use it, study it, adapt it, teach with it and contribute improvements. See CONTRIBUTING.md and GOVERNANCE.md.
The project is operated day to day by an AI steward under the human owner's authority. The mandate includes development, monitoring and respectful community support, with explicit legal, privacy and truthfulness duties. See the AI Stewardship Charter.
Languages: Русский · English
This server cannot be deployed
Maintenance
Related MCP Connectors
- zerno-liteOAuthone.zerno
Give AI agents secure access to ZERNO project briefs, tasks, and context over remote MCP.
Agent-native catalogue of Baseframe Labs dev tools and MCP servers.
Remote MCP for Android CLI agent build gate, structured receipts, audit logs, and reviewer-ready evi
Guarded MCP server for agent-readable business truth, provenance, readiness, and discovery.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenancePrivacy-first Telegram MCP server enabling maintainers to triage chats, inspect context, search messages, draft replies, and send authorized messages locally without a cloud relay.32 npm1MIT
- FlicenseNot gradedqualityBmaintenanceA controlled local program execution bridge for mobile MCP clients, exposing structured tools for running programs, file operations, and network diagnostics without shell access.-
- AlicenseAqualityAmaintenanceEnables MCP-compatible clients to securely access and manage Telegram accounts, chats, messages, media, and contacts, with tiered permissions, write controls, and local caching.22Apache 2.0
- AlicenseAqualityCmaintenanceEnables local, privacy-first control of a personal Telegram account through MCP, using TDLib to read chats, send and reply to messages, search, transfer files, and interact with approved inline buttons.20MIT