Create sharable sandboxed AI agents, loaded with your data

Amika lets you spin up shareable AI sandboxes for coding, automations, or vibe-coded apps. Connect your files and data, pick your favorite AI agent, and share with your team.

Claim your namespace

Your agents gets /home/{you} on the global filesystem

Almost there

Enter your email to claim /home/

Check your inbox

We just sent an email to . Please click the link to verify your email address, and then the namespace is yours!

View on GitHub Join Discord

~/workspace

▋

What Amika does

Amika is the home for your AI agents

Multiplayer coding agents

Run any Claude Code, Codex, or any AI agent in a local sandbox. Then host it to access it on the go or collaborate with your team.

Vibe-deploy your apps

Turn the result of your vibe-coding session into a deployed app or automation your teammates can use.

Connect your data and files

Connect your database, SaaS, and the web as a filesystem for your agent. We version everything so you can roll back agent mistakes.

Real Workflow

How I run sales every morning with Claude Code

Yes, only an engineer would run sales on a POSIX filesystem with a coding agent. But it works unreasonably well.

Agents sync data automatically

Three Claude agents kick off on a schedule: one scans my inbox for Bookface posts, one checks HubSpot tasks and drafts outbound emails, one monitors the YC Companies Directory.

Everything lands as files

All data goes into a network-mountable filesystem accessible from Claude Code or remote sandboxes like Modal and E2B. The outputs are just markdown files.

Review and iterate

I review the tasks and emails Claude prepared, ask it to make changes, or kick off follow-up automations. It's all files — easy to inspect, version, and share.

amika demo

Another example: Mount a Linear ticket and all related Notion docs into your sandbox and let your agent rip.

The Filesystem

How Amika's filesystem works

Scheduled data sync

Amika runs sandboxed scripts on a schedule that pull data from your tools — email, HubSpot, Linear, Notion, and anything else — and merge the output files into your filesystem.

Mount anywhere

Mount the filesystem into local VMs, remote sandboxes like Modal or E2B, or directly into Claude Code. Works anywhere you can mount a network filesystem.

Fine-grained access control

Control exactly how your agent interacts with data. Per mount, choose your access mode:

read-only

Agent reads files but can't modify anything

read-write

Agent reads and writes directly to your filesystem

overlay

Agent works on a copy — you decide what syncs back

amika.yaml

sources:
  hubspot:
    script: "./scripts/sync-hubspot.sh"
    schedule: "0 7 * * *"
    dest: "./sales/hubspot-tasks.md"
  gmail:
    script: "./scripts/sync-inbox.sh"
    schedule: "*/15 * * * *"
    dest: "./sales/inbox-leads.md"

mounts:
  claude-code:
    path: "./sales"
    access: "read-write"
  modal-sandbox:
    path: "./engineering"
    access: "overlay"

Roadmap

What's next

We're building more and would love feedback from power users of coding and computer agents.

Multiplayer agents

Multiple agents working together on the same filesystem — coordinating reads, writes, and tasks.

Versioning & branching

Version every file change. Branch your filesystem like git — per directory.

Built-in web scraping

Turn webpages into parts of your filesystem. The web as a data source, automatically.

Jobs & workflows

Run tasks in the background — on a schedule or triggered by an agent that's monitoring for changes.

Security controls

Prompt injection protection, sensitive data filtering, and audit logs for what your agent sees and writes.