Update to Fibery

Changed files

Choose a file to see its text changes. Binary or large files show metadata only.

.codex-plugin/plugin.json →

.codex-plugin/plugin.json

− removed · + added

--- before
+++ after
@@ -1,6 +1,6 @@
 {
   "name": "app-6a2ab6b4009c8191b74cb3b2c70025e3",
-  "version": "2.1.1",
+  "version": "2.1.2",
   "description": "Fibery is an operating system for orgs run by nerds: a modular work platform where you build the tools your team runs on. Startups, agencies, enterprises and non-profits use it for everything from product roadmaps and customer feedback to sales CRM, hiring, OKRs and client projects. Everything can link to everything else, so work never gets lost between teams.\n\nWith this plugin, you can do it all by talking to ChatGPT.\n\nDescribe how your team works, and ChatGPT builds it.\nSprints and bug tracking, a content calendar, a company wiki, or a process no template covers: explain it in your own words and ChatGPT sets up the databases, fields, workflows, views and automations. Want a priority field or a board grouped by stage? Just ask.\n\nWhen views aren\u2019t enough, ask for an app.\nChatGPT can build a custom app on your Fibery data, like a step-by-step intake form or a dashboard your CEO actually reads. Your data stays in Fibery, with its permissions and history intact.\n\nSketch it out on a whiteboard.\nAsk for a process flow, an org chart or a retro board, and ChatGPT draws the shapes, sticky notes, sections and arrows on a Fibery whiteboard, then rearranges them as your thinking changes.\n\nAsk the way you\u2019d ask a colleague.\n\u201cWhich customers asked for the features we shipped last month?\u201d \u201cWhat happened with the Acme deal this week?\u201d \u201cWho\u2019s still waiting on interview feedback?\u201d ChatGPT searches records, documents, comments and activity history to answer, and turns the answers worth keeping into live reports.\n\nLet routine work run itself.\nSet up rules and buttons in plain words: when a deal is won, create the onboarding project; when a bug turns critical, assign it and set a due date.\n\nPut your data to work.\nDraft release notes from what shipped this month, write a client update from open tasks, or turn interview notes into insights linked to the right features.\n\nAnd keep everything up to date.\nCreate and update records, move work along, assign people, write docs and leave comments, one at a time or in bulk, like turning meeting notes into assigned tasks.",
   "author": {
     "name": "Fibery Inc.",
@@ -40,31 +40,31 @@
             {
               "description": "Inspect workspace structure and query records.",
               "prompt": "Show me the structure of my workspace in Fibery (list of spaces and databases). Then list Stories which are in \"To Do\" state (include only name).",
-              "tools_triggered": "schema, schema_detailed, query",
+              "tools_triggered": "get_spaces, get_databases, query",
               "expected_behavior": "List the Software Development space with Release, Sprint, Story, and bug databases, and the fibery/file, fibery/user, and comments/comment system databases. Return these four Story names in To Do: In order to have fun as a programmer, I make bugs; In order to release something soon as a project manager, I can trim scope; Prepare Q3 launch; Prepare Q4 launch. Discover actual database and field names from the schema. Ordering is not significant."
             },
             {
               "description": "Create a temporary space, database, and fields, then remove the temporary space.",
               "prompt": "Create a \"Hiring\" space with a \"Candidate\" database that has a score field (number, integer) and an interview date field in my Fibery workspace. Then delete the space you just created. Include only whether the operations were successful and the names of the space, database, and fields. If Hiring already exists, stop and ask for another name instead of changing or deleting it.",
-              "tools_triggered": "schema, create_schema, delete_spaces",
+              "tools_triggered": "get_spaces, create_spaces, delete_spaces",
               "expected_behavior": "With no existing Hiring space, report successful creation of Hiring, Candidate, an integer score field, and an interview date field. Report successful deletion of the newly created Hiring space. If Hiring already exists, ask for another name without modifying it."
             },
             {
               "description": "Create an entity, update its workflow state, and delete that same entity.",
               "prompt": "Create a new bug in Fibery called \"Login fails on mobile\". Then update its state to \"In Progress\". Then delete this entity. Include only whether creation, updating, and deletion were successful, and what field values were present in the entity.",
-              "tools_triggered": "schema, schema_detailed, create_entities, set_state, delete_entities",
+              "tools_triggered": "get_spaces, get_databases, create_entities, set_state, delete_entities",
               "expected_behavior": "Creation succeeds with Name Login fails on mobile, Priority Medium, and State To Do in the supplied test workspace. Updating State to In Progress succeeds, then deletion succeeds. Use the ID of the newly created bug for both subsequent operations; leave any pre-existing records with the same name unchanged. Report returned or verified values rather than assuming defaults."
             },
             {
               "description": "Read and summarize the Release Notes document attached to an entity.",
               "prompt": "Find the release with name \"1.0\" in Fibery, then read its Release Notes and describe what is in there in 2 sentences.",
-              "tools_triggered": "search, schema, schema_detailed, query, get_fibery_skill, read_document",
+              "tools_triggered": "search, get_spaces, get_databases, query, get_fibery_skill, read_document",
               "expected_behavior": "Locate release 1.0 and its Release Notes document; load get_fibery_skill with skill documents before read_document. Summarize in two sentences: Release 1.0 introduces dark mode, advanced search filters, and support for five additional languages, alongside performance, UI, accessibility, and speed improvements. It fixes several bugs, removes iOS 12 support, and notes high CPU usage on some Linux systems as a known issue. Equivalent wording is acceptable when grounded in the document."
             },
             {
               "description": "Create a grid view and then delete that same view.",
               "prompt": "Create a table view in Fibery for the bug database. Include name, priority, effort and state fields. Then delete the view you just created.",
-              "tools_triggered": "schema, schema_detailed, create_view, delete_views",
+              "tools_triggered": "get_spaces, get_databases, create_view, delete_views",
               "expected_behavior": "Create a view with viewType grid for the discovered bug database and its Name, Priority, Effort, and State fields. Delete only the newly created view using its returned ID. Report successful creation and deletion and the four selected fields."
             },
             {