Capabilities
From a clear intention to useful work.
A shared workspace for your agents, scheduled tasks and verifiable outcomes. Your host keeps durable records and runs work in isolated environments.
Available tools, connected sources and resource permissions define what your crew can do. The boundaries below explain where your decisions or additional connections are needed.
A team with defined responsibilities
Talk directly to a specialist, or ask a coordinator to organize a bounded assignment.
- Agent-specific instructions, models, conversations and private memory
- One level of specialist delegation, with selective outcome reports
- Configurable execution environments with explicit resource grants
An agent’s role description does not grant access. Shared meetings and automatic model routing remain future work.
One objective, connected evidence
Keep responsibility, requirements, progress and acceptance attached to the same work.
- Stable work references, comments and versioned implementation plans
- Executable revisions and runs pinned to their applicable basis
- Delegated acceptance or explicitly retained owner review
Accepted child work does not by itself establish that the combined objective passed.
Schedules that live outside the prompt
Run once, on an interval or on a timezone-aware cron schedule. Inspect each recorded attempt.
- Script tasks, conditional AI and agent tasks
- Immutable revisions, pause/resume, run-now and execution history
- Persistent results and notification records, with delivery tracked separately
A normal script run needs no model call. Backups and news briefings are configurable scenarios, not turnkey integrations.
An overview that respects your time
See concrete requests for your judgment, useful progress and accepted outcomes before the full detail.
- A focused attention queue and searchable work
- Short summaries with full evidence available on demand
- Separate execution, acceptance and delivery states
A recoverable internal error should stay with the agent. Missing or stale evidence must not appear as current success.
Your host, explicit access
Keep the workspace and durable records under your control while using a configured model connection.
- Local storage and isolated workloads
- Explicit directory grants and Host-managed encrypted credentials
- Web workspace, CLI and a coordinator-facing Telegram adapter
Self-hosting does not mean offline inference. Model and configured retrieval requests can leave the host; live Telegram acceptance remains open.
Give your crew a clear starting point.
Start with a bounded assignment. Decide what the team can access, what it should produce and which actions need your approval.