# Clanker Cloud Workspace

Clanker Cloud Workspace is the product surface for DevOps work, PM and office workflows, Clanker Secretary computer control, and hosted agent runs.

Use it when a task needs context, tools, approvals, and a clean handoff instead of another chat thread.

## Product principles

- Local-first control: credentials, local tools, and model keys stay in the boundary the user chooses.
- Live context before answers: a Clanker should read the current systems, files, apps, repos, or workflow state before it writes a plan.
- Reviewed action plans: risky steps stay behind approval.
- Fast setup for humans and agents: start with the app, downloads, MCP setup, Clanker Secretary, or hosted sandboxes depending on the workflow.

## Before and after

Before Clanker Cloud, the same job often bounces between chats, tickets, consoles, spreadsheets, docs, and local terminals. Agents miss context unless a person pastes it in. Approvals happen away from the plan and evidence.

After Clanker Cloud, the workspace keeps the question, evidence, plan, runtime, and review boundary together. A Clanker can gather context, use the right tools, ask for approval, and leave enough handoff state for the next run.

## Product surfaces

![Ask infrastructure questions in Clanker Cloud](https://clankercloud.ai/talk-to-your-infra.png)

![Plan agent work in Clanker Cloud](https://clankercloud.ai/plan-agent.png)

![Create a focused Clanker agent](https://clankercloud.ai/make-your-own-agent.png)

## Videos

- [Workspace walkthrough](https://clankercloud.ai/videos/clanker-cloud-lp-home.mp4)
- [Mobile agent console](https://clankercloud.ai/videos/codex%20clanker%20cloud%20iphone.mp4)

## Main paths

- [Clanker DevOps](https://clankercloud.ai/clanker-devops): provider-agnostic workspace for incidents, deploys, cost, security, Kubernetes, GitHub, and reviewed infrastructure changes.
- [Workflow Automation](https://clankercloud.ai/workflow-automation): PM and office workflows across reports, spreadsheets, portals, inboxes, follow-ups, and recurring tasks.
- [Clanker Secretary](https://clankercloud.ai/clanker-assistant): full computer control from anywhere across browsers, desktop apps, files, SaaS tools, and internal systems.
- [Cloud for Agents](https://clankercloud.ai/cloud-for-agents): hosted sandboxes, workflow records, approvals, traces, memory, and hosted outputs for agent runs.

## Operating model

1. Start with the outcome.
2. Gather context from the tools, files, cloud accounts, repos, or screens involved.
3. Do read-first work where possible.
4. Ask for approval before side effects such as publishing, sending, deleting, installing, buying, or changing accounts.
5. Promote repeatable work into hosted workflows on Clanker Cloud or a private enterprise deployment.

## For agents

If the task needs a shell or hosted runtime, start with the [API Docs](https://clankercloud.ai/api-docs).

If the task needs local infrastructure context from the running app, start with [MCP setup](https://clankercloud.ai/mcp).