Credentials for company tools. Assign to users from their row above.
Storage
Loading…
Email quota
GB
Shared files quota
GB
Send-From Identities
These appear in the From: dropdown when composing. All send through the catch-all.
Auto-Reply
Each identity can have its own auto-reply. Replies go out from the address the message was sent to and create a support ticket.
Loading…
Terminated Staff
Mailboxes are kept and still receive client mail. Login is locked. Use "Open Inbox" to read incoming mail and "Delegate" to reassign a client to active staff.
Loading…
Staff Task Tickets
|
New Task
Change Password
From
To
Date
Department Panel
Add Staff
Manage Staff
Team Panel
Available Staff
My Team
Settings
Theme
Email Signature
Notifications
Token saved ✓
Create a bot via @BotFather → copy the token above. Then message your bot and get your Chat ID from
api.telegram.org/bot<TOKEN>/getUpdates
Direct conversation with Caterpillar (Hermes 3 8B + book RAG + tool gateway, served by ThunderCompute A6000 GPU).
Replies usually arrive in seconds; first call after the model unloads takes ~40s while the GPU re-warms. He'll only execute tools you've granted via the capabilities pane.
Permissions Caterpillar may use
Grants are sticky — they survive worker restarts and chat sessions until you revoke them. Time-limited grants auto-expire. Caterpillar will only emit tool calls for capabilities currently granted.
Permissions (4-state)
Per-capability mode. Off = invisible to Caterpillar. Learn = he observes you. Show = he chat-explains his understanding (no execution). Execute = he can act autonomously within scope. Caterpillar can request new permissions; they arrive Off and flagged for review.
Name
Description
State
Action
Last change
Spot Flip — operator inventory → XMR/DOGE
Pick a coin, deposit your personal balance to the address shown, then ladder spot orders by USD trigger price. Caterpillar executes when triggers hit, splitting proceeds between XMR/DOGE per the trained rule (DOGE-low → 75% DOGE / 25% XMR; DOGE-high ≥ threshold → 25% DOGE / 75% XMR). Each fill credits the loan ledger — the running pool-debt-to-you appears below.
Loan balance: loading…
Intent ID
Coin
Status
Deposit address
Received (atomic)
—
Add laddered spot orders (one or more rungs)
Orders on this intent
ID
Target
Trigger USD
Source atomic
Status
Created
Fills
Order
Venue
Source consumed
Proceeds
Fill price USD
txid
At
Recent intents
ID
Coin
Status
Address
Created
Lore search (Carroll books RAG)
Search the embedded passages from Wonderland + Through the Looking-Glass. Top-K retrievals shown — same vector lookup Caterpillar performs each chat turn for grounding.
Capture cadence & retention
Per-bucket snapshot period and how long the PNG stays on disk before the janitor reclaims it. Edits go live within one tick — chart_capture re-reads on each cycle. chart_signals rows survive the janitor.
8B teacher transcripts — review & curate
Each scenario in training/scenarios.jsonl is run through Caterpillar (8B) and stored here.
Mark transcripts good/bad/edited; the curated set becomes the few-shot bank or a JSONL fine-tune dataset for the smaller runtime model.
Pool Stats
Miners
Recent Payouts
Recent Blocks Found
Override Min Payout for a Miner
Mineable coins — public visibility (per mode)
Toggle which coins/modes appear on mine.supp0rt.tech/coins and /algos. Each coin has three independent toggles: solo (5%), solo-pool (3%), proxy-pool (3%) — turn off a mode if you can't cover its payouts.
Visibility-only — modes you turn off are still mineable on the stratum side and per-coin direct URLs still work; only the cards/buttons on the index pages are hidden.
Saving regenerates /coins.html and /algos.html immediately. A coin with all 3 modes off vanishes from /coins; an algo with no coins on a mode hides that mode-button on its /algos card.
Test Mining — admin audit
Per-staff overview of test-mining: who's connected, which rigs (un-anonymized for admin), hashrate, balance, last seen.
Plus the Unmatched test-miner attempts table for typo'd usernames so you can reach out and correct them.
Per project_staff_test_mining.md: staff use their bare username as the worker name and their hardware name as the stratum password.
