KEEP DESK // PUBLIC INSTALL FREE // SELF-HOSTED

KEEP DESKfree · local · ollama

OtaconsKeep · Multi-agent Command Deck

Own the desk.
Command the bots.
Keep the data.

Why hand your computer to Meta Muse or Grok? Named AI teammates. One always-on computer. Real browser. Real jobs. A Why dossier that refuses to celebrate the wrong cart. Local, Grok & Muse-class computer-using AI on a workstation you own.

Get the Install Watch the Deck Beat the cloud?

FREE · PUBLIC REPO · SELF-HOSTED · Videos at bottom ↓ · What "91.6% claimable" means

00 // Watch the Deck

Best Keep Desk clip, on the page

Command Deck, LIVE handoffs, Done + Why. Full YouTube embed also lives under Videos.

Open on YouTube → · 30s GIF preview

01 // Why it exists

Cloud teammates are cool.
Owning the desk is better.

Meta Muse and Grok proved the genre: persistent teammates that drive a computer while you walk away. They also proved the tax: your work, browsing, and files on someone else’s machine, forever, behind a subscription, with an agent loop you can’t fully autopsy when it carts the wrong SKU. Keep Desk is the local answer: the same kind of computer-using teammate, running on hardware you actually own.

No cloud landlord

Prompts, screenshots, research MD, desk files, LAN by default. The brain is Ollama. Cloud LLM endpoints are refused.

Operator cinema

Command Deck UI. LIVE browser. Codec bar. Batch pipelines. Why dossiers. Mission control, not another chat bubble farm.

Honest failure

Hollow / Incomplete / off-brief. A mission cannot silently celebrate the wrong cart. That alone is worth the build.

02 // Intel board

Scored. Not vibes.

Authoritative scorer on the reference Keep, compliance_score.py · 2026-09-19.

91.6%Claimable

87.3%Raw

PASSCritical gate

69PASS rows

Browser L5-prod gate: PASS, 51 authed @ 90.2%, HIR 2.1%
Counts: 69 PASS · 5 PARTIAL · 5 FAIL · 10 NOT_TESTED
~75% day-to-day feel vs a polished cloud desk is a separate operator estimate (model quality + mobile + connectors + desktop). Do not collapse it into 91.6%.

03 // Comparison

Keep Desk vs typical cloud teammates

Cloud wins on frontier models and zero-ops. Keep wins on sovereignty, cost ceiling, and an inspectable desk you actually own. Competitor names change; the local-vs-cloud tradeoff does not.

	Keep Desk	Typical cloud teammate
Where the computer lives	Your box / LAN	Provider cloud
Brain	Your Ollama model	Provider frontier model
Cost	Hardware + power only	Subscription + often usage
Named persistent bots	Yes	Often yes
Browser computer-use	Yes	Often yes
Full desktop GUI agent	No (known FAIL)	Varies
Local-only LLM	Enforced	Usually no
Self-host	Yes · public repo	No
Frontier quality OOB	Your GPU model	Usually stronger out of the box

04 // Install

Docker Compose + Ollama

Keep Desk is a public repository. No seat, no license key, no gate. Linux host recommended. GPU strongly recommended.

git clone https://github.com/Otaconskeep/keep-desk.git
cd keep-desk
cp .env.example .env

# Point at local Ollama (cloud LLM bases are refused)
# LOCAL_OLLAMA_URL=http://host.docker.internal:11434/v1
# LOCAL_MODEL=gpt-oss:20b

ollama pull gpt-oss:20b
docker compose up -d --build

# Command Deck → http://127.0.0.1:5765/
# Browser service → http://127.0.0.1:5766/

Ports: 5765 Command Deck / API · 5766 browser
Desk volume: files, bot memory, screenshots, workspace/research/<pipe_id>/
Smoke test: transmit a short research order; confirm Why is not hollow after completion
Doctrine: bots are workers, gate money, deletes, and public posts

Full INSTALL.md

Deep troubleshooting, Obsidian vault mounts, upgrades, uninstall, in the repo: Otaconskeep/keep-desk.

Need a hand?

Discord, or open an issue on the repo.

05 // Honest limits

What Keep Desk is not

Not a frontier cloud model, local 20B-class plans thinner than Grok/GPT on nasty sites.
Not a full desktop GUI agent, browser-first; native apps out of claimable scope.
Not production-safe alone, bots are workers; gate money and public posts.
Not zero-ops, you run Docker, Ollama, and disk backups.
Amazon SPAs still bite, shopping stages now require browser_navigate first (no web_research-only theater; hollow shortlists blocked). Bot walls / SPA choke can still need retries or human takeover.
LIVE honesty, idle parks on NO SIGNAL on purpose; active shopping must leave park onto real product pages.
Authenticated sessions are PARTIAL (matrix BROW-07 / BROW-08), fixture cookies persist; live SaaS human-auth takeover and resume are not solid enough yet to claim unattended “leave it logged in and walk away.”
Not true parallel bots yet (matrix D-02), several bots can own jobs, but one worker drains the queue serially. Concurrent computer-use like cloud Muse/Grok multi-task is still a gap.
L6 endurance is unproven, L5-prod critical gates PASS; the 12h/24h unattended tier (BROW-L6) is still IN PROGRESS, so “runs a day alone” is not a claim yet.

06 // FAQ

Quick answers

Is Keep Desk free?

Yes. Running locally has no cloud LLM bill, and the repo, install instructions, and compose wiring are public, no seat, no license key.

Does it phone home to OpenAI or xAI?

No. Local Ollama only; cloud LLM endpoints are refused.

What does 91.6% mean?

91.6% is an internal weighted claimable requirements score (critical gates PASS on Keep Desk’s own matrix in Otaconskeep/keep-desk). It is not a completion bar for OtaconsKeep overall, and not “91.6% as good as Grok.” Self-estimate is ~68% Grok feature-parity and ~85% for this lab’s actual use case; day-to-day feel is lower once you count model quality, mobile, connectors, serial workers, and L6 endurance still in progress.

Why was LIVE stuck on NO SIGNAL during shopping?

Earlier builds nudged web_research first, so Amazon jobs never moved the browser. Fixed: shopping/homelab stages must browser_navigate before finish; empty shortlists are rejected.

Can it buy things with my card?

Treat purchases as dangerous. Research is in scope; production spending needs human approval and external gates.

Who built this?

Antonio G. Garcia, Otaconskeep.

07 // Doctrine