Provide a pre-enrolled sandbox repository for new-user experimentation

[fullsend-ai-triage]

Note

This issue was automatically generated from meeting notes by the scribe agent.
Please review, edit, and add any missing context before prioritizing.

Problem

New users evaluating fullsend face a significant onboarding barrier: they must complete full GCP project setup and CLI installation before they can experiment with the system. Users without access to a billable GCP project or management approval cannot try the platform at all. A pre-enrolled sandbox repository would let users experience the agentic workflow without the infrastructure overhead.

Options considered

• Dedicated public demo repo pre-enrolled in fullsend with all agent roles active, allowing users to open issues and see triage/code/review in action. Trade-off: requires ongoing maintenance and token spend.
• Template repo with mock responses that simulates the workflow without live agent runs. Trade-off: less realistic but zero operational cost.
• Shared sandbox org with time-limited access for evaluators. Trade-off: access management complexity.

Acceptance criteria

• A repository exists that is pre-enrolled in fullsend with triage, code, and review agents active
• Users can open issues and observe the full agent workflow without personal GCP setup
• Documentation links to the sandbox repo as a "try it" entry point
• Access model is defined (public read, controlled write, or fork-based)
• Cost and token budget for sandbox usage is estimated and bounded

Related

• Builds on Onboarding: GCP project barrier #1216 (Onboarding: GCP project barrier)
• Related: Public community–use shared GitHub Apps #914 (Public community-use shared GitHub Apps)
• Related: SPIKE: community token mint on GCP vs Cloudflare port #915 (Community token mint hosting spike)
• In progress: docs: add simplified install guide for admins #1483 (simplified install guide)
• Source: Meeting notes

[fullsend-ai-triage]

Thanks for filing this — the onboarding barrier is a real pain point and this captures the problem well.

Before this can be prioritized, one key decision is needed: which of the three options should be pursued?

1. Dedicated public demo repo — live agents, realistic experience, ongoing cost
2. Template repo with mock responses — zero cost, less realistic
3. Shared sandbox org with time-limited access — realistic but adds access management overhead

Each option has a very different implementation scope, infrastructure requirement, and maintenance burden. Could whoever attended the meeting (or a maintainer) indicate which direction the team is leaning? If no consensus was reached, would it make sense to open a design doc or ADR to evaluate the trade-offs more formally?

This would also clarify the downstream questions around access model and token budget that are listed in the acceptance criteria.

---

Labels: Feature request related to onboarding/install experience with no priority yet assigned.

[ifireball]

We can use the "fullsand" org for extra hilarity...

[fullsend-ai-triage]

This issue was previously triaged and a clarifying question was asked about which of the three approaches to pursue, but no decision has been posted yet. The question remains the key blocker for making this actionable.

To reiterate: the three options (dedicated public demo repo, template repo with mocks, shared sandbox org) have fundamentally different implementation scopes and ongoing costs. A developer cannot start work until the team picks a direction.

Could a maintainer or someone from the meeting indicate which option the team is leaning toward? If no consensus was reached, consider opening a short design doc or ADR to evaluate the trade-offs — the acceptance criteria around access model and token budget will flow directly from that choice.

---

Labels: Feature request related to the install/onboarding experience; no priority assigned yet since the approach hasn't been decided.

[ifireball]

To the triage question: We would probably want a whole org with several repos that people can play with. As people come to sessions, we might let them clone heir own repos into it to try fullsend on them