agentleFS
Sign inStart free
BuFi007BuFi007/open-agents/.agents/skills/remove-demo-limits/SKILL.md

remove-demo-limits

Skill1 starsChanged 5 months agoMITView on GitHub

Removes Open Harness hosted demo restrictions from a fork. Use when a maintainer wants to remove managed-template trial caps, hosted deployment gating, or "deploy your own" limits. Triggers on "remove demo limits", "remove trial limits", "remove hosted restrictions", "open this up for my fork", "remove managed template restrictions".

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. About 0 are common, 13 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈13

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Remove the managed-template trial restrictions with the smallest coherent change.

    line 6
  2. Distinctive:

    no trial session cap

    line 10
  3. Distinctive:

    no trial message cap

    line 11
  4. Distinctive:

    no hosted-only restriction errors

    line 12
  5. Distinctive:

    no hosted-demo delete restrictions

    line 13
  6. Distinctive:

    no dead helper code or stale tests

    line 14
  7. Distinctive:

    Read these files before editing:

    line 17
  8. Distinctive:

    Remove the guards that block session creation, chat messages, or message deletion for managed-template users.

    line 36
  9. Distinctive:

    If the auth callback still blocks non-Vercel emails on hosted deployments, remove that restriction too.

    line 37
  10. Very specific:

    Delete apps/web/lib/managed-template-trial.ts if it becomes unused.

    line 38
  11. Distinctive:

    Remove or update tests that assert the hosted caps, delete restrictions, or hosted-only auth gating.

    line 39
  12. Distinctive:

    Do not add feature flags, env toggles, or new dependencies.

    line 40
  13. Distinctive:

    Keep unrelated auth, session ownership, and sandbox behavior unchanged.

    line 41
  14. Distinctive:

    if a failure is pre-existing, say that clearly and separate it from your changes

    line 46

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Remove the managed-template trial restrictions with the smallest coherent change.

Goal

Make the fork behave like a normal self-hosted deployment:

  • no trial session cap
  • no trial message cap
  • no hosted-only restriction errors
  • no hosted-demo delete restrictions
  • no dead helper code or stale tests

Inspect first

Read these files before editing:

  • apps/web/lib/managed-template-trial.ts
  • apps/web/app/api/sessions/route.ts
  • apps/web/app/api/chat/route.ts
  • apps/web/app/api/sessions/[sessionId]/chats/[chatId]/messages/[messageId]/route.ts
  • apps/web/app/api/sessions/route.test.ts
  • apps/web/app/api/chat/route.test.ts
  • apps/web/app/api/sessions/[sessionId]/chats/[chatId]/messages/[messageId]/route.test.ts

Then search for these identifiers and strings to catch older or newer variants:

  • isManagedTemplateTrialUser
  • MANAGED_TEMPLATE_TRIAL_
  • deploy-your-own
  • open-agents.dev
  • vercel.com
  • This hosted deployment includes
  • does not allow message deletion

Required changes

  1. Remove the guards that block session creation, chat messages, or message deletion for managed-template users.
  2. If the auth callback still blocks non-Vercel emails on hosted deployments, remove that restriction too.
  3. Delete apps/web/lib/managed-template-trial.ts if it becomes unused; otherwise simplify it so no dead exports remain.
  4. Remove or update tests that assert the hosted caps, delete restrictions, or hosted-only auth gating.
  5. Do not add feature flags, env toggles, or new dependencies. Prefer deleting the restriction code outright.
  6. Keep unrelated auth, session ownership, and sandbox behavior unchanged.

Verification

This repo uses Bun. After the edits:

  • run bun run ci
  • if a failure is pre-existing, say that clearly and separate it from your changes

Output

Report:

  • which restrictions were removed
  • which files changed
  • verification result

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free