Owned operating product · Multi-agent system

AgentDesk

A personal agent system that reviews messages, identifies what matters and prepares decisions. A person reviews the suggestion and chooses the action.

New agent in AgentDesk: Bybit Guardian Discuss a similar system

New agent in AgentDesk

Bybit Guardian

Skip the exchange. See what needs attention.

An agent that watches your Bybit plan: purchases, order execution, results and what needs attention. Reports and explained alerts arrive in Telegram. You make the decisions.

Discuss my monitoring needs

Bybit Guardian Telegram

See what arrives in Telegram

Six views, from the overall picture to an alert’s cause. Choose a scenario or browse the carousel.

Overview

Your account at a glance

Equity, margin status and data freshness come together in a concise summary. When attention is needed, the reason is right there.

  • Equity and margin balance.
  • Current mode with an explanation.
  • Last confirmed account snapshot.
Telegram/bybit
Bybit GuardianAn AgentDesk agent
Illustrative data
Account overviewBYBIT

Last confirmed snapshot

18,420.50 USD

Account equity

Margin balance
16,280.20 USD
Liabilities
3,000.00 USDT
MMR
4.2%
IMR
36.1%
Review needed

Take-profit coverage gap · SOL

Access: read-onlyALARM · 5 min

Orders

Every order has a clear state

Partial purchases, open positions and take-profit orders have distinct states. See what has filled and where a review is needed.

  • Fill percentage and active remainder.
  • Position state separate from order state.
  • Take profit: waiting, filled or a coverage gap.
Telegram/bybit_orders
Bybit GuardianAn AgentDesk agent
Illustrative data
Plan and ordersBYBIT
P/L, USDT+38.40 / −124.80
Illustrative plan: purchases, positions and take profit
AssetBuyPositionTake profitP/L
BTC100%OpenActive+82.40
ETH100%OpenTrigger−96.20
SOL46%+OpenGap−111.00
ADA0%—Planned0.00
SOL · 46% +

Partial purchase. Order remainder is active. Take-profit coverage needs a review.

3 of 4 assets have purchasesExample plan

Results

Profit and loss you can explain

Realized results stay separate from unrealized results. The chart shows change over time, and coverage shows how complete the calculation is.

  • Plan results in USDT.
  • Confirmed fills and fees.
  • Charts spanning up to six months when history exists.
Telegram/bybit_chart
Bybit GuardianAn AgentDesk agent
Illustrative data
Plan performanceBYBIT
Realized
+38.40 USDT
Unrealized
−124.80 USDT
P/L historyUSDT · 7 days
0-80-160-240MonTueWedThuFriSatSun
Plan total−86.40 USDT
Valuation: 4/4 assetsFees confirmed

Risk

Debt and maturities stay in view

Margin metrics, collateral and liabilities are shown separately. Each loan has its own maturity; unknown limits are never guessed.

  • Initial and maintenance margin.
  • Debt by currency and collateral.
  • Contracts, maturities and repayment reminders.
Telegram/bybit_risk
Bybit GuardianAn AgentDesk agent
Illustrative data
Risk and liabilitiesBYBIT
MMR · maintenance
4.2%
IMR · initial
36.1%

Initial-margin limit is not confirmed

Liabilities3,000.00 USDT
Loan maturities
LoanUSDTDue
011,000.00In 14 days
022,000.00In 30 days

Collateral: BTC · ETH · USDT

Each contract has its own due dateRead-only

Alerts

An alert explains what needs attention

The agent detects a take-profit coverage gap and switches to frequent checks. You see what needs reviewing; the decision remains yours.

  • The reason for entering alarm mode.
  • Polling every five minutes in alarm mode.
  • Incomplete data is explicitly marked.
Telegram/bybit_mode
Bybit GuardianAn AgentDesk agent
Illustrative data
Alert reasonBYBIT
ALARMReview needed

Take-profit coverage gap

SOL

Buy
46% · partially filled
Order remainder
Active
Take profit
Coverage incomplete
Polling mode
Every 5 minutes

Decision and action stay with the owner

Weekly review

A weekly review without rebuilding the history

Purchases, debt changes, observed peak margin load, results and data gaps come together in one review.

  • Changes over the last seven days.
  • Morning, evening and weekly summaries.
  • Observed peaks are based on saved snapshots.
Telegram/bybit_week
Bybit GuardianAn AgentDesk agent
Illustrative data
Weekly reviewBYBIT

Last seven days · illustrative review

Plan result−86.40 USDT
Assets with purchases
3 / 4
Debt change
−200 USDT
Observed peak MMR
4.6%
Needs attention
Take-profit gap · SOL
09:00Status21:00SummarySun 19:00Weekly

The peak comes from saved snapshots, not continuous recording.

Anonymized report reproductions based on the presentations. All figures, assets and maturities shown are illustrative; this is not a live account.

Anonymized report reproductions based on the presentations. All figures, assets and maturities shown are illustrative; this is not a live account.

What Guardian handles for you

Plan and orders

  • Buy states: waiting, partial or full fills, and cancellation.
  • Fill percentage and the remaining order’s state.
  • Open positions separate from buy-order status.
  • Take-profit states and coverage gaps.

Results you can explain

  • Realized and unrealized results in USDT.
  • Cost basis from actual fills and confirmed fees.
  • Position history: entries, partial sales and closing.
  • Charts spanning up to six months when history exists; calculation coverage stays visible.

Risk and liabilities

  • Equity, margin balance, initial and maintenance margin metrics.
  • Debt by currency, collateral and individual loan contracts.
  • Repayment reminders at 30, 14, 7, 3 and 1 day.
  • Overdue loans and alert reasons, including take-profit gaps.

Scheduled summaries and event alerts

  • Polling every 120, 30 or 5 minutes according to mode.
  • Morning status at 09:00 and evening summary at 21:00 Moscow time.
  • Weekly review on Sundays at 19:00 Moscow time.
  • Round-the-clock event alerts after a successful poll.

Privacy and bounded access

  • Read permissions checked before collecting data.
  • The agent cannot buy, sell or withdraw funds.
  • History and plans are encrypted at rest.
  • Detailed reports go only to the confirmed owner; credentials remain isolated.

Data and monitoring health stay visible

  • The last confirmed snapshot and its freshness.
  • Visible data gaps instead of invented zeroes.
  • Mode, history, plan and queue survive restarts.
  • Independent polling and delivery checks; ambiguous sending requires review.
Modes, schedule and all commands

Monitoring adapts to the situation

Rules determine polling frequency and explain why attention is needed. Returning to normal requires several consecutive successful checks.

Normal
120 min

Routine monitoring of the agreed plan.

Watch
30 min

More frequent checks when conditions change.

Alarm
5 min

Frequent polling with an explicit alert reason.

09:00 morning status and chart · 21:00 evening summary · Sunday, 19:00 weekly review. All times are Moscow time.

These are polling intervals, not a continuous price feed. Events are detected on the next successful poll; commands use the latest saved account snapshot, while quotes for profit and loss are refreshed separately.

From a summary to the details, in Telegram

Account status, risk, orders, charts and the weekly review are available on command in the owner’s private environment.

/bybit
Account status and data freshness
/bybit_risk
Risk, debt, collateral and loan maturities
/bybit_orders
Purchases, positions and take-profit coverage
/bybit_chart
Charts for the agreed plan
/bybit_chart all
A combined chart for the entire plan
/bybit_week
Review of the last seven days
/bybit_mode
Current mode and reasons for attention
/bybit_help
Abbreviations, symbols and units

Read-only account access. The agent cannot buy, sell or withdraw funds. Decisions and financial actions remain with the owner; monitoring does not remove market risk.

Basis: two owner-provided presentations dated 7 November 2026 with examples of real reports. This is dated capability evidence, without a new independent server or recovery check. Monitoring is configured for a confirmed account, plan and private route.

Many events. One owner’s attention.

Mail, commercial opportunities and financial data all compete for attention. The September record already covered six mailboxes and five portfolio sources. The new Bybit Guardian adds a dedicated monitoring path for an account, orders and liabilities, while decisions stay with the owner.

The core AgentDesk agent flow

  1. 01

    Incoming events

    Mail and notifications from six mailboxes

  2. 02

    Read and apply rules

    The event is normalized and assigned a permitted route

  3. 03

    Specialized analysis

    • Mail triage
    • Freelance scout
    • Personal messages
    • Investment signals

    AI helps prepare context and a suggestion

  4. 04

    Owner decision

    A person reviews the suggestion and decides what to do

Shared foundation

Persisted state · authority boundaries · diagnostics · decision history

Bybit Guardian

A separate path: Bybit account and orders → rule-based checks → Telegram summaries and alerts → owner decision. Financial data is read-only.

Explore the new agent
The core mail flow from the 0.14.1 record: four areas, shared state and rules. This is a process diagram, not a screenshot or a new production check. The five shared-portfolio sources and the new Bybit Guardian are shown separately.

Fact → evidence → boundary

Evidence record

Public extract: Dated evidence for release 0.14.1 ·

  1. Four agents handle distinct incoming events

    Evidence
    Mail triage, freelance scouting, personal messages and investment signals share state and rules. Six mailboxes were checked at the verification point.
    Boundary
    This record covers the core 0.14.1 release. Bybit Guardian has separate November evidence; September checks do not verify it.
  2. Five sources recovered through the normal path

    Evidence
    The release record reports successful first-attempt collection for every source and 559 checks in each of the local and server artifact suites.
    Boundary
    This establishes recovery on the release date, not current health, and discloses no financial data.
  3. A suggestion does not automatically become an action

    Evidence
    Sending mail, accepting work and financial decisions remain with the owner. Portfolio sources are read-only.
    Boundary
    The system does not trade and is not presented as an autonomous executor.

The date belongs to the source record. Reading it is not a new check of the operating system.

Different event streams. One agent system.

The mail path retains four specialized areas. Shared-portfolio collectors and the new Bybit Guardian run alongside it as separate monitoring paths. An independent news stream remains future work.

Operating

Mail and notifications

Mail Triage reviews incoming messages, determines priority, and selects a safe route. It is one input stream, not the system’s sole purpose.

Operating

Commercial opportunities

Freelance Scout performs Limited-Information preselection: OPEN for further review, SKIP for silent retention, and manual review on failure. This is not a decision to accept a job; detailed analysis remains a separate step after owner clarification.

Operating

Personal messages and replies

Personal Message Agent handles email notifications of direct contact. It links replies to existing opportunities only through stable identifiers; unlinked messages are still delivered. Drafting is optional and sending remains manual.

Operating

Investment events and monitoring

Investment Signal reviews incoming notifications; five isolated collectors form the shared portfolio. Bybit Guardian separately monitors an account, orders and risk, delivering summaries to the owner. The system has no trading authority.

Possible expansion

News and information noise

A possible scenario: specialized agents separate relevant news from repetition and noise, collect context around selected topics, and prepare a concise review.

From incoming signal to owner decision

A shared process routes each event to a specialized agent through explicit rules. AI assists semantic review, the Supervisor prepares the result for the owner, and the decision and state are persisted.

  1. Signals

    Mail already received: general notifications, opportunities, direct messages, and investment events.

  2. Read-only intake

    Bounded reading without downloading attachments or opening links.

  3. Policy and routing

    Code normalizes the event, applies rules, and selects a specialized handler.

  4. Specialized agents and AI

    Domain-specific review depends on the scenario. Semantic enrichment is used only where it adds value.

  5. Supervisor

    Prepares the result for the owner. A separate delivery layer chooses a Telegram topic or direct message without changing the business decision.

  6. Owner decision

    Approve, Edit, Skip, or confirmation of an action already completed manually.

  7. Persisted outcome

    Decisions and state are persisted. Mail and proposals are sent manually; a separate component applies authorized mail labels.

A shared foundation, not a collection of bots

Mail Triage, Freelance Scout, Personal Message Agent and Investment Signal share an agent registry. Bybit Guardian adds a separate rule-based monitoring path: code determines calculations and modes, while financial decisions remain human.

Mail intake

Normalization, classification, attention policy, and safe routing for incoming mail.

Opportunities

The model extracts evidence with quotes and code applies a frozen policy. OPEN does not mean readiness to accept the job; SKIP is retained in history without notification.

Owner approvals

The human receives a bounded action set and retains the final decision.

Operations

The historical record connects delivery, mail cycles, four agents and five collectors. Guardian also tracks snapshot freshness, polling and delivery; a delayed chart does not block risk checks.

Five independent sources, one confirmed portfolio

In the verified release, five independent collectors read broker, crypto tracker and manual register data through one source adapter contract. A collector failure does not replace its last confirmed snapshot or stop the others.

Brokers · source 1

A read-only API and confirmed broker-native snapshot with no trading authority.

Brokers · source 2

Read-only data; negative cash is retained as a liability while short securities are rejected.

Manual register

One private CSV contains a complete snapshot and explicit owner-provided USD values; an incomplete file is not published.

Crypto tracker

GET-only holdings are reconciled with the reported total; crypto retains source-local identity.

Brokers · source 3

Isolated trade-api-read access, safe token rotation, and strict reconciliation across configured accounts.

Isolated collectors → confirmed canonical snapshots → one USD denominator → deterministic allocation → a privacy-safe Telegram projection.

For the shared portfolio, absolute values, quantities and account identifiers stay in private financial state; Telegram receives the allowed privacy-safe projection. Bybit Guardian has a separate private route: detailed reports go to the confirmed owner and credentials are never sent there. Both paths only read financial data.

What the owner receives

These anonymized cards show the system’s output in operating scenarios. Mail and commercial streams provide examples; they do not limit the product to email processing.

#SYSTEM · AgentDesk

The foundation at work

Mail, Scout, Digest, delivery, health, and queues form one operational picture.

Mail
operating
Scout
operating
Delivery
controlled
Queues
no stuck work
  • Current health is derived from the actual operational snapshot.
The system is observed as one operating environment, not a set of unrelated scripts.

#TASK · PRELIMINARY

Commercial opportunity

A notification is compressed into a preliminary assessment, reasons to continue, risks, and missing context.

Assessment
preliminary
Context
task details required
Links
not opened
  • Missing context is not disguised as a confident proposal.
EditAlready repliedSkip
A notification becomes a decision with explicit uncertainty and three owner actions.

#TASK · FINAL

Prepared presale

Once sufficient context is available, the system produces fit, material risks, a recommendation, and a personalized draft.

Fit
final assessment
Recommendation
conditional after risk review
Sending
manual by the owner
  • Assessment remains separate from polished copy: risks stay visible beside the proposal.
EditAlready repliedSkip
From opportunity to prepared response—with manual sending and a persisted status.

#SECURITY · HIGH

An event requires verification

An untrusted message is recognized as important, but verification is directed through the service’s official interface rather than a link in the message.

Priority
high
Verification
official interface
External action
not performed
  • Message content remains untrusted input and cannot change system authority.
Security is part of the workflow: the decision is persisted and no external action is performed.

What matters technically

Each boundary addresses a practical risk: losing a message, repeating an action, prompt injection, false confidence, or excessive authority.

  1. Stable core + optional AI

    Decision
    Normalization, scoring, routing, policy, and presentation belong to code. AI performs bounded semantic work.
    What it provides
    AI failure simplifies the outcome without breaking the core workflow.
  2. Authority bounded by the system

    Decision
    Roles and access are separated and AI tools are denied. The collector is read-only; a separate Mail Marker may add authorized service labels, but cannot send or delete mail.
    What it provides
    A classification error does not automatically become an action in an external service.
  3. State is persisted

    Decision
    Decisions, queues, checkpoints, and delivery lifecycle are stored in SQLite before the next step.
    What it provides
    A restart continues from known state instead of guessing the previous outcome.
  4. Ambiguous failure is not retried blindly

    Decision
    If the network may have accepted a message before disconnecting, delivery enters an explicit uncertain state without an automatic duplicate.
    What it provides
    The system prefers visible manual review over sending the same decision twice.
  5. Mail remains untrusted input

    Decision
    Links are not opened by default, attachments are not downloaded, and AI output passes strict schema validation.
    What it provides
    Incoming text cannot expand a component’s tools, route, or authority.
  6. Human-in-the-loop is part of the product

    Decision
    Missing context, high-cost errors, and final sending explicitly return the decision to the owner.
    What it provides
    Autonomy expands gradually while a working manual path remains available.

Current status. A private working system. Bybit Guardian is documented in materials dated 7 November 2026; the core 0.14.1 release record was verified on 19 September 2026.

Historical core release record · 19 September 2026

The AgentDesk 0.14.1 record pins the deployed code, Linux artifact, recovery of five collectors and diagnostics on that date. The new Bybit Guardian is described above using separate November materials; September checks do not verify Guardian.

Production 0.14.1 recovered

All 559 local and Linux checks passed. The patch repaired four collector executable modes, the schedule activation boundary, and shared missed-cycle evidence.

All five sources refreshed

After release, one idempotent all-source refresh completed all five collectors for brokers, the crypto tracker and the manual register successfully on the first attempt; the connected snapshot was confirmed.

Health views agree

At the verification point, Mail 6/6 and agent ticks 4/4 were fresh, issues and unfinished deliveries were empty, SQLite integrity was ok, and foreign-key violations were zero.

Authority remains bounded

Mail and proposals are sent manually, and no trading actions exist. Full-Information Mode and an independent news source are not claimed as complete.

Where this approach applies

AgentDesk demonstrates how to combine specialized agents, AI, business policy, read-only integrations, human decisions, and operational diagnostics. The approach applies to presales, CRM, documents, alerts, and controlled data aggregation.

The four cards above are anonymized reconstructions of previously verified messages. The private Telegram environment and financial data are not a public demo. The core release record is dated 19 September 2026, and the Bybit Guardian description is dated 7 November 2026; these materials do not guarantee continuous availability after those points.

Which checks compete for your attention?

Tell us which messages, data and changes you have to check manually. The atelier can help define monitoring scope, notification rules and the actions that should remain human.

Discuss a similar system