Skip to main content
The Cloud Computer is Notis’s own private workspace in the cloud. Whenever a task needs more than a chat reply — installing something, running a script, transforming a file, browsing the web — Notis does it here. You don’t set anything up. It’s on by default for every Notis user. Most users meet the Cloud Computer through Skills. A skill tells Notis how to do the work; the Cloud Computer gives it the environment to execute it.

​
What you can ask for

  • “Turn these receipts into a clean expense spreadsheet.”
  • “Open this website, capture the pricing table, and tell me what changed.”
  • “Create a PowerPoint from this outline using our brand template.”
  • “Run my weekly social-media-review skill and schedule the winning posts.”
If the task can be done end-to-end without your machine, this is where it happens.

​
Install anything to extend Notis

When a task needs a tool Notis doesn’t ship with, just ask — Notis can install CLIs, npm packages, and Python libraries on the fly and use them right away. A few examples:
  • “Install the GitHub CLI and list my open PRs across all repos.”
  • “Use yt-dlp to download the audio of this YouTube video and transcribe it.”
  • “Install ffmpeg and trim the first 30 seconds off this video.”
  • “Use pandoc to convert this Markdown into a nicely formatted DOCX.”
  • “Install Vercel CLI and deploy the static site in this folder.”
  • “Install the Stripe CLI and pull last month’s payouts as a CSV.”
  • “Use ImageMagick to resize every PNG in this zip to 800px wide.”
Once installed inside the workspace, the tool stays available for follow-up requests in the same session.

​
What’s in the box

The Cloud Computer comes ready to work. Out of the box it can:
  • Open and edit PDFs, Word docs, spreadsheets, and slide decks.
  • Run Python and Node scripts.
  • Browse and extract data from websites.
  • Read images and run OCR on scanned files.
  • Use any Skill you’ve installed.
Common built-in skill families:
  • Documents — PDF, DOCX, XLSX, and PPTX creation and editing.
  • Browser Agent — navigation, extraction, screenshots, and form workflows.
  • Data cleanup — CSV, spreadsheet, and structured-data transformations.
  • Publishing workflows — research, drafting, formatting, and uploading to connected apps.

​
Sending and receiving files

  • Send — attach files to your message. Notis can use them right away.
  • Receive — when Notis creates a file (a report, a spreadsheet, a deck), it comes back in the same thread. Depending on the request, Notis may also save it straight to Notion, Google Drive, Gmail, or another connected app.
For sensitive files, follow the same rule as with any assistant workflow: only upload what you’re comfortable letting Notis process. See Privacy & Security.

​
Good requests

Be specific about the final artifact and where it should go:
“Create an XLSX with one sheet per month, include formulas, and send it back here.”
“Use the browser agent to capture screenshots of the onboarding flow, then make a bug report.”
“Use my blog-post skill to draft the article, save it to Notion, and attach a Markdown copy here.”

​
When Notis uses it

Always, unless the task truly needs to happen on your own computer. If a request can be answered directly from chat, integrations, or memory, Notis won’t bother spinning anything up. For everything else, this is the default — fastest, safest, and works on any channel. You can inspect every step from the agent timeline in the Desktop and Web App, and enable Dev Mode when you want the raw tool calls and outputs.

​
FAQ

No — you get one Cloud Computer per account, reused across every thread, channel, and skill run. That means a CLI you install in one chat is still available in the next one, and files you generate stick around between conversations until the workspace recycles.
It stays running as long as you’re actively using Notis, then shuts down after a period of inactivity to free resources. The next time you ask Notis to do something, a new one spins up automatically — you don’t have to do anything.When the workspace recycles, anything Notis installed mid-session (like an npm package or a CLI) is gone and will be reinstalled on demand the next time it’s needed. Files you’ve explicitly saved (to Notion, Drive, the thread itself, etc.) are unaffected — those live outside the workspace.
No. Your Cloud Computer is private to your account. It’s isolated from every other Notis user and from the wider internet except for the network calls Notis explicitly makes on your behalf.
Back to the thread you’re in, as attachments. If you ask Notis to save somewhere specific — Notion, Google Drive, Gmail, an email reply — it’ll do that too. Files don’t stay stuck inside the workspace.
Yes. Long-running tasks continue in the background and Notis pings you in the same thread when they finish — you don’t have to keep the chat open.
It’ll install it. CLIs (gh, ffmpeg, yt-dlp, pandoc, …), npm packages, and Python libraries can all be added on the fly. If a task needs credentials or access Notis doesn’t have, it’ll ask you to connect the missing integration instead of guessing.
  • Skills — instructions and templates Notis can run.
  • Local Shell — when work needs to happen on your machine instead.
  • Desktop Use — when Notis needs to drive a real app on your desktop.