765TFLOWCommunity
Request access

Field notes · from the shop

Community

Field notes — installation, supported AI clients, and jobs that have actually run. Not a forum. We publish after we read what you send.

01 / Notes

Notes

  1. 765TConnect Flow to your AI clientFlow integrates with multiple AI channels so you can work in the client you already know. The installer currently registers Claude Desktop, Claude Code, Cursor and Codex; other MCP clients follow after compatibility testing.SetupMCPRevit
  2. 765TThe BIM knowledge library is off by defaultWe keep a BIM knowledge library as a product asset. It is not switched on in the default runtime. What runs today is the execution gate — preview, authorize, execute, verify.PlaybookMCP
  3. 765TThe live path is preview, authorize, execute, then verifyYou describe the outcome. Flow plans, runs, and reports back with what changed and the element IDs. The gate sits inside that path — it is not a click on every element, and it is not a self-driving modeler.MCPPlaybook

02 / Send a note

Send a note

Email is enough. Owner reads it, then publishes it into the site. Nothing you send appears automatically.

Email a note
  1. 01

    Write in Vietnamese or English. One concrete tip beats a survey of the product.

  2. 02

    Do not send client files, UniqueIds, PDF/RVT/RFA, or model screenshots that identify a job.

  3. 03

    Do not include passwords, tokens, machine paths, or installer binaries.

  4. 04

    Name the client you actually used: Claude Desktop, Claude Code, Cursor or Codex. ChatGPT is not supported yet.

  5. 05

    Email is the path. If you already work in the public repo, you can also open a pull request next to the existing notes.

Public repo: github.com/meococ/765T-Flow-feedback. Email first — we read it, then we publish.