$0 idlepersistent agent workspaces over MCP

    Workspaces for Humans and Agents.

    Starspace keeps your repo, docs, notes, and generated files alive between sessions. Agents can read, search, write, cite, and publish through one MCP endpoint without paying to keep a VM warm.

    Start a workspaceRead the docs
    Persistent filesystemSemantic searchMCP-ready tools

    1,000 free credits / month · No credit card required

    Agents can hand work off cleanly.The workspace is the memory.

    A cloud agent can leave files, notes, and citations behind. A local agent can pick them up hours later. The shared filesystem persists without a keep-warm bill.

    Agent A
    Cloud agent · background run
    running
    $ grep -r 'session' /repo
    → found 47 matches
    $ cat auth/refresh.ts
    $ edit /notes/auth-audit.md
    ✓ wrote 234 lines
    workspace
    starspace.run · ws_a82
    idle
    $0.00
    /repo
    auth/
    refresh.ts
    /notes
    auth-audit.mdjust now
    /docs
    spec.pdf
    2 agents connected0 ops/min
    Agent B
    Local agent · on demand
    ready
    $ cat /notes/auth-audit.md
    → 234 lines from Agent A
    $ ask "what's the next step?"
    → answered (3 citations)
    $ edit auth/refresh.ts

    Each agent only needs the workspace contract: durable files, searchable context, and clear handoffs, with no idle meter ticking.

    Core product

    Not another chat wrapper.

    Starspace is the shared workspace layer your agents plug into when they need durable files, search, and source-grounded answers.

    Workspaces that survive everything

    Push code, docs, and notes once. The workspace remains available across agent sessions, IDE restarts, and overnight cloud runs. Idle costs nothing because there is no VM to keep warm.

    starspace-cli, 80×24
    $starspace push my-project
    → uploaded 142 files (8.2 MB)
    → indexed for semantic search
    ✓ workspace ready
    Idle cost
    $0.00 / mo
    Stays alive
    forever
    Close your laptop. Come back later. Still here.

    Every agent meets here

    One MCP endpoint for Claude Code, Claude Desktop, Cursor, and custom agents. Your workspace becomes a set of durable tools your agent already knows how to call.

    MCP Endpoint
    starspace.run/mcp/ws-823
    ACTIVE
    Claude Code
    Claude Desktop
    Cursor
    Codex CLI
    Tools your agent gets:
    fs_readfs_writegrepaskpublish

    Mix code, docs, PDFs, and ask one question

    A repo, a 90-page spec, and meeting notes can live together. The ask tool returns source-grounded answers with line ranges, page numbers, and enough context to verify the result.

    ask
    “Where does auth token refresh happen, and which spec section governs it?”
    2 sources cited from one workspace
    From repo
    auth/refresh.ts
    L142–L168
    From upload
    spec.pdf
    p47 §4.3.2
    answered
    confidence: high
    Starspace CLI

    One push to
    a workspace every agent can use.

    starspace push uploads your folder. starspace connect wires it into your MCP client. Agents can read, search, and edit files without copy-paste or browser extensions.

    CLI docsView sourcePyPI
    starspace : zsh
    $pip install starspace-cli
    ✓ installed starspace-cli 0.2.0
    $starspace push ./my-project
    → uploaded 142 files (8.2 MB)
    → indexed for semantic search
    ✓ workspace ready
    $starspace connect claude
    → paste this into claude_desktop_config.json
    "starspace": { "url": "…" }
    restart Claude, your workspace is online.
    How it works

    From local folder to shared agent memory in three steps.

    01 · Load context

    Push a repo or document set

    Upload files once. Starspace stores the filesystem and builds the search index your agents will reuse.

    $ starspace push ./project
    02 · Connect tools

    Attach any MCP client

    Claude Code, Claude Desktop, Cursor, or a custom agent gets read, write, grep, ask, and publish tools.

    $ starspace connect claude
    03 · Keep working

    Share, cite, and publish

    Agents continue from the same state later. Publish a folder when you need a quick live URL.

    $ starspace publish ./site
    Use cases

    Built for agents that need more than a prompt window.

    Starspace sits under the chat UI as persistent infrastructure: files, retrieval, and collaboration state.

    Long-running code work

    Push a repo once, then let agents return to the same files and notes across many sessions.

    Shared team knowledge

    Give every teammate and every agent one source of truth for docs, specs, and decisions.

    Quick publishing

    Turn a generated folder into a live URL without standing up a deploy pipeline first.

    Custom agent storage

    Use MCP tools for durable read, write, search, and handoff state between autonomous runs.

    Source-grounded analysis

    Ask across code, PDFs, notes, and docs with citations that point back to the exact source.

    Research corpora

    Search and summarize large collections without re-uploading context into every chat window.

    No keep-warm tax

    What persistence should cost.

    VM-backed sandboxes usually bill for time while a machine is reserved. Starspace bills for workspace operations, so durable context can sit idle without becoming a monthly server bill.

    VM-backed sandboxes

    Always-on compute / background-agent sandboxes

    Idle, kept warm 24/7
    reserved compute keeps billing
    $20–45 /mo
    Active, 10K ops / month
    $25–50 /mo
    Active, 100K ops / month
    $30–80 /mo

    Useful when you need compute. Wasteful when you only need durable state.

    Starspace

    Starspace

    Per-call billing on edge functions

    Idle
    no reserved VM to keep warm
    $0.00 /mo
    Active, 10K ops / month
    ~$0.50 /mo
    Active, 100K ops / month
    ~$5 /mo

    The workspace can persist without an idle meter. You pay for what agents actually do.

    Illustrative estimates; actual costs vary by provider, workload, and configuration. See Starspace pricing for current rates.

    Simple plans, no idle charges.

    Start free, then scale workspace count, storage, operations, and API keys when your agents get busier.

    Free

    $0forever

    Persistent workspaces. Per-call billing. Try the whole product.

    • 1 indexed workspace + 1 sandbox workspace
    • 500K tokens indexed per workspace
    • 100 MB storage
    • 1,000 workspace operations / month
    • 1 API key

    Hobby

    $7/ month

    For solo builders shipping side projects.

    • 5 indexed workspaces + 5 sandbox workspaces
    • 5M tokens indexed per workspace
    • 1 GB storage
    • 5,000 workspace operations / month
    • 5 API keys
    Popular

    Pro

    $19/ month

    For power users running real workflows.

    • 100 indexed workspaces + 100 sandbox workspaces
    • 50M tokens indexed per workspace
    • 10 GB storage
    • 20,000 workspace operations / month
    • 25 API keys

    Team

    Contactus

    Shared workspaces, SSO, audit logs.

    • Everything in Pro
    • Shared workspaces & RBAC
    • Audit log
    • SSO
    • Private deployment options
    Ready when you are

    Stop rebuilding context every time an agent starts.

    Create a workspace, connect an MCP client, and let your agents keep useful state between runs. Idle workspaces stay free.

    Start freeSee setup guide
    Prefer a human? Email ace@starspace.run