Set up with AI

Paste the short “Deploy and connect” prompt into an AI tool that can read web pages. It can read installation paths, first-run setup, and verification steps from llms.txt; llm.txt serves the same content.

A coding agent with project and terminal access can help edit configuration, start the service, and verify requests. A chat assistant with web access only can explain the docs and prepare a plan; you or a coding agent still need to execute it. Use “Read and plan” for an overview, or “Configure my project” to connect to an existing instance.

Make the docs available

Links in a prompt do not automatically provide the page content to an AI tool. If it cannot access the web, paste the quick start, relevant package-manager page, and cache verification guide instead of relying on guessed instructions.

Copy a prompt

Deploy and connect

Copy for an AI assistant

Please read https://depsilo.com/llms.txt, then help me deploy Depsilo and connect this project for my environment. Reuse an existing instance if available. Complete first-run setup, then verify requests and cache results.

Read and plan

Copy for an AI assistant

Read the official Depsilo v0.11.0 documentation first:
https://depsilo.com/en/docs/
https://depsilo.com/en/docs/get-started/
https://depsilo.com/en/docs/package-managers/
https://depsilo.com/en/docs/verify-cache/
https://depsilo.com/en/docs/agents-mcp/

I want to use Depsilo to proxy and cache dependencies for my project. Based on these docs, explain what it does and its limitations, how to start the server and complete first-run setup, how to select the correct package-manager endpoint, and how to verify request routing and artifact cache hits separately. Distinguish metadata requests, artifact requests, and the client's local cache; repeated installs do not prove server cache hits. First ask about my deployment environment, the service URL reachable from the client, the package managers used in my project, and whether I use HTTP or HTTPS. Then provide an ordered plan with links to the relevant docs.

Base commands and capabilities only on v0.11.0 pages you have read. If a page is inaccessible or describes another version, ask me to paste the relevant page; do not guess endpoints or versions. Do not request, retain, or repeat the bootstrap token, administrator password, or API token. At this stage, plan only; do not edit files or run commands.

Configure my project

Copy for a coding agent

Help me use Depsilo v0.11.0 in the current project. Read these pages first:
https://depsilo.com/en/docs/get-started/
https://depsilo.com/en/docs/package-managers/
https://depsilo.com/en/docs/verify-cache/
https://depsilo.com/en/docs/agents-mcp/
Then read the page for the package manager used in this project. If the pages are unavailable or describe another version, ask me to provide the v0.11.0 content; do not invent configuration values.

1. Inspect the repository's package managers, current registry/index settings, and lockfiles without making changes. List the proposed files and verification commands. Do not change host, user-level, Docker daemon, or global package-manager settings without my approval.
2. Confirm the Depsilo URL reachable from my client (HTTP or HTTPS) and whether the server is already running. If not, choose the documented Docker or binary installation for my environment and propose a deployment pinned to v0.11.0 with persistent state; wait for my approval before running it. I will enter the bootstrap token and administrator password in the Portal myself.
3. Once I approve the files, change only the necessary project settings with an explicit command, project, or virtualenv scope. Preserve lockfiles, other configuration, and existing integrity checks. Add this instance's plaintext HTTP exceptions only when required for HTTP, keeping existing entries for other sources. Never write passwords or tokens to the repository, command output, or AI conversation.
4. Check /ready from the client environment, make a dependency request, and match its metadata or index record in Admin Access logs. If I need to inspect the logs, give me the time, package, and request type to find. Then follow verify-cache to obtain the artifact URL returned by the instance, download it twice independently with curl, and check the matching artifact hit records. Do not construct download URLs by hand or substitute repeated installs or metadata hits for artifact verification. The first request may already be a hit. The guide uses an npm example; package files from other ecosystems need their own verification.
5. Report the configuration scope, request routing and artifact cache results, rollback steps, and anything you could not verify. If the client's local cache avoided a server request, do not claim server verification is complete.

Do not treat depsilo init-agent or read-only MCP tools as operations that automatically configure the client. Do not remove an existing service, state volume, or configuration without asking first.

Next steps

• If you do not have a running instance, follow the quick start to complete protected first-run setup.
• Configure only the package managers you actually use. The Portal shows configuration generated for the current instance address; it does not edit your project files.
• Follow Verify caching to check artifact downloads and hits separately, distinguishing verified traffic from results that still need confirmation.
• For reviewable agent instruction files or read-only MCP access, see Agents and MCP.