You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Twenty team - would you be open to a small contribution around your existing agent/plugin infrastructure?
I noticed Twenty already has substantial AI-agent surface area: packages/twenty-codex-plugin, packages/twenty-claude-skills, Cursor Skills, MCP docs/server support, and CI around the Codex plugin. So I would not propose adding a new plugin from scratch.
The contribution I have in mind is narrower:
add versioned eval cases for the existing Twenty Codex/Claude Skills workflow
add optional Telvine publishing/listing docs for teams that want a public distribution handle, plugin version history, component inventory, and metadata-only telemetry
clarify the relationship between the installable plugin and the Skills/capabilities inside it
keep CRM/customer data out of telemetry and eval fixtures
The plugin would remain Twenty-owned and installable through the existing Twenty harness paths. Telvine would only be an optional distribution/eval/metrics layer for teams that want to track adoption and production behavior.
Would a scoped PR in packages/twenty-codex-plugin / packages/twenty-claude-skills be useful, or would you prefer this stay outside the repo?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi Twenty team - would you be open to a small contribution around your existing agent/plugin infrastructure?
I noticed Twenty already has substantial AI-agent surface area:
packages/twenty-codex-plugin,packages/twenty-claude-skills, Cursor Skills, MCP docs/server support, and CI around the Codex plugin. So I would not propose adding a new plugin from scratch.The contribution I have in mind is narrower:
The plugin would remain Twenty-owned and installable through the existing Twenty harness paths. Telvine would only be an optional distribution/eval/metrics layer for teams that want to track adoption and production behavior.
Would a scoped PR in
packages/twenty-codex-plugin/packages/twenty-claude-skillsbe useful, or would you prefer this stay outside the repo?All reactions