implemented.stream
Built with

Cursor & agents ​

implemented.stream development is designed to run in Cursor with Cloud Agents, optional Bugbot review, and repository secrets for deploy.

Cursor Cloud Agents ​

  • Run autonomous tasks against Origin agensdklab/devstacks (build, deploy, zip merge, docs).
  • Store Cloudflare and Gemini credentials in the Cursor Cloud Agent Environment — never commit tokens to git.
  • Agents should follow Build & deploy for production changes.

Bugbot ​

Automated PR review on Origin (docs).

Turn on (if Bugbot “หาย” / never runs) ​

  1. Cursor → Automations → Bugbot — connect Origin, then enable repo agensdklab/devstacks (Origin requires per-repo toggle; unlike default GitHub connect-all).
  2. Draft PRs — default Bugbot skips drafts. Either mark PR Ready for review, or enable Reviews on draft PRs in your personal Bugbot settings, or use repo config (this repo sets triggers.drafts: true in .cursor/config/bugbot.yaml on main after merge).
  3. Manual run — comment on the PR: bugbot run or cursor review.
  4. Checks — on GitHub you see Cursor Bugbot; on Origin, look for Bugbot comments/status on the PR timeline (PR #5 had no checks while draft).

Repo config ​

See .cursor/config/bugbot.yaml in this repository (drafts: true, review on each push).

MCP & integrations ​

Use MCP servers configured in Cursor (Cloudflare, GitHub, Google Drive, Context.dev, etc.) for research and operational tasks. OAuth MCP flows stay in the IDE; document new tool bindings on Tools when they affect shipped UI.

Branding on site ​

The docs theme may show Cursor in the aside credit and footer social links (cursor.com, GitHub org) as the primary IDE/agent surface for this stack — separate from third-party framework marketing sites removed from the footer.

Repository ​

© 2026 implemented.stream