AI agent sandboxes for real work.
A useful answer sometimes needs a calculation, a document, or working code. Ghost has managed workspaces for those jobs, with tools for the task and room to keep the files you will need again.
Code, data and documents · Reusable workspace files · Part of Ghost
Give the task a place to run.
- Playground
- Process a dataset or create a document.
- Trader
- Research market data and test stated assumptions.
- Publisher
- Build and maintain a durable managed app.
Put the work in the room that fits.
The homepage introduces three rooms. Explore what each is for: general computation in Playground, financial research in Trader, and durable apps in Publisher.
Start with the kind of work.
Different tasks need different environments. A quick data transformation, a reusable research workflow, and a managed web app should not all be treated as the same job.
Playground does the file and data work.
ghost can use Python, document libraries, and media tools in a separate runtime. Reusable files live in the workspace; a temporary process is not the same thing as a persistent service.
Turn the research into a review deck.
Trader gives financial work its own workspace.
Market data, analysis, and backtesting tools support a reproducible research workflow. Keep sources and assumptions explicit; a simulation is not a forecast or a live trade.
Test a thesis against historical data.
- Input
- Source-identified price history
- Method
- A stated strategy and assumptions
- Output
- Results, limitations, and a reviewable report
Publisher keeps durable apps together.
A managed app has its own source and coding work. After the app is checked, exposure creates a route; recording the verified publication keeps the catalog in sync.
Illustrative jobs, not live runs or financial results. Sandbox limits vary by deployment. A sandbox is an execution environment, not authorization to trade or publish.
An execution workspace inside your assistant.
An AI agent sandbox is a separate environment where an assistant can run code and work with files. Ghost uses managed workspaces for computation, financial research and durable applications. The workspace supplies the tools; your request supplies the purpose. A sandbox is not permission to publish, trade or access unrelated data.
Playground handles the file and data work.
Turn a source file into something you can use: parse a PDF, organize spreadsheet data, create a chart, prepare a presentation, or convert media. Playground gives Ghost a Python runtime with document, data-analysis and media tools.
Reusable work belongs in the persistent workspace. A source dataset, an intermediate result and the final document can stay available for a later request without repeating every preparation step.
A working note can hold the brief and source links, while Research helps gather and assess the public evidence. The sandbox performs the computation; it does not decide that an unsupported source is trustworthy.
- Data
- Dataframes, calculations and charts.
- Documents
- PDFs, spreadsheets, Word documents and presentations.
- Media
- Inspection, conversion and generated files.
- Delivery
- Check the artifact and return it through the appropriate file workflow.
Files can outlast the process.
Workspace persistence and continuous execution are different things. In Playground, files saved to the workspace can survive a container stop, reset or recreation. Temporary files and running processes do not have that same guarantee.
Normal cleanup can remove the runtime after a run. An explicitly requested continuous service follows a separate managed lifecycle; it is not what every analysis task becomes.
CPU, memory, workspace capacity and execution time are bounded and can vary by deployment. If a job reaches a limit, Ghost should explain the limitation instead of presenting a partial result as finished.
Keep what the next run needs.
- Reusable
- Input files, scripts and generated artifacts saved in the workspace.
- Temporary
- Scratch files and current process state.
- Next run
- Reuse the saved files; restart computation when needed.
Different work needs different environments.
Trader gives financial research a dedicated workspace with market-data, analysis, visualization and backtesting tools. Sources and assumptions still matter. A historical simulation is not a forecast, and the workspace does not authorize live trades.
Publisher is for a durable application you want to maintain. Its app-specific coding session handles source, dependencies and build work. A verified runnable app is distinct from a public route and a recorded publication.
Use Coding agents for the software task and Publishing for the managed app lifecycle. One-off scripts and experiments belong in Playground.
- Playground
- General computation, document creation and experiments.
- Trader
- Financial data, research methods and backtesting.
- Publisher
- Durable app identity, coding work and explicit publication.
A useful workspace has boundaries.
Playground and Trader use constrained runtimes. They are non-root, do not expose the Docker socket, and keep writes within their supported workspace and temporary locations. Their toolkits are designed for the work, not unrestricted host administration.
Network access is available. A sandbox is therefore not a claim that all processing is offline or that a task can never affect an external service. Your requested scope and any applicable approvals still matter.
Local Mac files enter through the appropriate approved transfer workflow. If the task genuinely requires local OS state, Ghost has a separate Computer capability rather than treating the sandbox as your Mac.
An environment is not authorization.
- Requested work
- Analyze the supplied data and save a reviewable report.
- Not implied
- Trade, publish the report, or collect unrelated files.
- Handoff
- Return the result with the source and any remaining limitation.
Product details
Sandboxes, at a glance.
Supported work, useful outputs, and what to check before you start.
- Workspaces
- Playground handles code, files, and media; Trader supports market-analysis work; Publisher owns durable apps and their release workflow.
- Artifacts
- Commands can produce documents, datasets, charts, or app files in the selected workspace. Keep the result with the environment that owns it.
- Setup
- Tool availability, network access, and resource limits depend on the workspace. Uploading a host file is an explicit transfer, not automatic access to the Mac.
One assistant. Connected work.
Ghost is a personal AI assistant for Mac. Its meetings, notes, tasks and execution tools are capabilities of the same product—not separate assistants you have to brief from scratch.
A note can hold the brief, Research can supply the evidence, and a sandbox can turn the inputs into a file or an app. Coding agents handle supported software work; Publishing handles the requested delivery of a durable application.
- Notes
Keep the inputs, brief and source record.
- Research
Find and assess the evidence for the task.
- Coding agents
Give software work a scoped coding session.
- Publishing
Maintain and publish a verified managed app.
- Computer
Use local tools when the task needs your Mac.
Questions about sandboxes in Ghost.
Is Ghost an AI sandbox API?
This page describes execution workspaces inside the Ghost assistant. It is not a claim that Ghost sells a general-purpose sandbox SDK or infrastructure service for arbitrary third-party agents.
What can the Playground sandbox create?
Supported tools cover data analysis, plots, documents, presentations and media processing. The available inputs, libraries, deployment limits and requested output determine what a particular task can complete.
Do my files disappear when the sandbox resets?
Files in the persistent workspace can survive runtime reset or recreation. Temporary files and running processes do not. Persistence is not an unlimited-storage or backup guarantee.
Does a sandbox run all the time?
Not by default. Ordinary runs have cleanup and runtime limits. Continuous services require an explicit request and a separate managed lifecycle; persistent files alone do not keep a process alive.
Does Trader place stock orders?
Trader provides a research and execution environment, not automatic authority to trade. No broker credentials are built into the base image. Research, simulations and generated reports should not be confused with live orders.
Does creating an app publish it?
No. Managed apps must be built and checked, exposed through a confirmed route when requested, and explicitly recorded as published. A successful coding task is not itself a public launch.
Are the workspaces unlimited or guaranteed secure?
No. Resource and execution limits vary by deployment, and isolation is not an absolute security guarantee. Ghost should keep the task scoped, explain limitations and use the relevant approval boundaries.
Go from a request to a usable result.
Give Ghost the source material and the task. Use the workspace that fits, then keep the result connected to your work. Ghost is in private beta for macOS.
Request access