Changelog

Every product change, newest first. Each entry describes what shipped, not what is planned. Longer write-ups are on the blog, and how-tos are in the docs.

  1. Procedures that use your Apps, and one tool catalog for every AI

    Scheduled Procedures now read Recruit CRM, Exa, and your other connected Apps, can start when a candidate moves stage, and every AI gets the same eleven tools.

    Scheduled Procedures read your Apps

    A Scheduled Procedure run can now call your connected Apps as tools while it works, such as searching Recruit CRM or the web through Exa, to gather exactly what the Procedure asks for. Tool calls run one at a time, in order.

    If a run calls no tools at all, CompanyOS says so: its content isn’t backed by Workspace data, and you can decide whether to trust it.

    The emailed briefing is now always the briefing itself, never the model’s raw output.

    Start a Procedure when something changes in Recruit CRM

    Besides daily and weekly timing, a schedule can now start when a Recruit CRM record moves to a stage you pick. A candidate reaching “Interview” can trigger an interview-prep briefing to the people who need it. Connect Recruit CRM under Integrations to use it. See Scheduled Procedures.

    Run now also goes through the same queue as scheduled runs, so a manual run behaves exactly like a real one.

    One tool catalog, in every AI

    Claude, ChatGPT, and Codex now get the same eleven tools: search, fetch, and list_files for knowledge; find_, use_, and store_ for Procedures and Templates; and find_apps and call_app for connected Apps. See AI Clients.

    • Everyone can write. Any Member can now save a Procedure or Template as a Personal draft from their AI, then share it. An Owner approves it before the team sees it.
    • Apps are discoverable. Your AI finds what’s connected with find_apps and uses it with call_app, including Recruit CRM candidate search and Exa web search.

    Also in this release

    • The map on Home is easier to read: connections are visible, and the layout settles and fits the page.
    • CompanyOS stays free during the beta. Billing for seats is built, and stays off until it opens. See Beta and pricing.

  2. Better answers, connected knowledge, and clearer procedures

    Search now explains what it finds, the same knowledge reaches your AI assistant, and procedures keep schedule and history in one place.

    CompanyOS now makes shared knowledge easier to understand and recurring work easier to manage. This note covers what is in the current product, not a promise of features still to come.

    Search that explains what it finds

    Search brings together matching text, related meaning, and connections in your workspace knowledge. You get a source-backed summary next to ranked results, so you can read the answer and open the evidence behind it.

    People, topics, and documents connect to a search on a larger graph you can explore. You see up to ten file results by default, with ranks to help you navigate the evidence. Related procedures and templates appear next to document knowledge. Parsed document content, including Word files, opens as readable text instead of unreadable file data.

    CompanyOS knowledge, inside your AI assistant

    Homepage search and connected AI tools now use the same knowledge engine. Assistants receive the sources, relationships, and context they need to work with the results.

    We removed the embedded search panel from the MCP experience. Your assistant can present the answer in the conversation, with a short search status and the supporting context behind it. CompanyOS also supplies its logo to clients that support it.

    Workspace and personal-file permissions still apply wherever you search.

    Procedures with everything in one place

    Procedure details now bring together the procedure itself, its parameters, schedules, and run history. You can see what will run, how it is configured, and what happened afterwards without moving between disconnected screens.

    Retrying a specific run creates a new attempt for that run, so recovery stays tied to the original history. You set a first-run date, local time, timezone, and daily or weekly recurrence; scheduling follows your local time across daylight-saving changes. Run and delivery details distinguish generated content from notification problems.

    Emails you can preview, and drafts you control

    CompanyOS briefings use a clearer email layout, with readable headings, tables, and source links. Owners can preview a sample before scheduling, and preview the saved briefing from a completed run.

    Microsoft 365 email actions create drafts for review and sending from Outlook. CompanyOS does not send them. CompanyOS platform notifications stay limited to members of the workspace.

    A clearer knowledge graph

    Graph settings are simpler to review and edit, and you can rebuild the graph when you need to refresh connections. Graph suggestions publish as part of processing, without a separate approval step.

    Processed files can contribute their evidence to the knowledge graph more consistently.

    Try searching for a person, project, or topic on your CompanyOS homepage, or ask your connected AI assistant to search CompanyOS, and follow the sources and relationships from there.

  3. Scheduled Procedures: CompanyOS runs it and emails the result

    Owners can now schedule a published Procedure. CompanyOS runs it over Company Files and connected Apps, and emails the briefing to the Members who need it.

    Until now, a Procedure only ran when someone asked their AI to run it. Owners can now put one on a schedule.

    Schedule a Procedure

    Open a published Procedure and choose Schedule. Pick daily or weekly, a start time, and a timezone. Choose the Members who receive it, and whether everyone gets the same email or CompanyOS runs once for each of them.

    Each run reads the Procedure and its Templates, gathers what it needs from Company Files and the Workspace’s connected Apps, and emails the result from CompanyOS. If a run fails, the Owner gets a notice instead of silence.

    See and control every run

    Each Procedure lists its schedules and its runs. Run now starts a run straight away, and Owners can stop a schedule at any time.

    Microsoft 365 drafts, without the extra approval

    Preparing an email in Microsoft 365 no longer needs a separate CompanyOS approval step. Connecting your mailbox is the permission, and every email action still creates a draft that you review and send from Outlook.

    Search shows how sources connect

    Search results now include the relationships between the files they found, in the app and in your AI. Members can also Redo graph on a single file from its X-ray view.

    Read more in Scheduled Procedures.

  4. SharePoint sites, and sharper file reading

    Owners can bring SharePoint Online sites into CompanyOS, scanned documents and images read better, and search ranks passages more precisely.

    SharePoint Online

    An Owner can now connect SharePoint Online for the Workspace and pick which sites to bring in. Documents from those sites sync into Files, so search and every connected AI can cite them like any other Company File. CompanyOS asks for read access only.

    The Integrations page is simpler too: each App has one row, and connecting happens in its side sheet. Exa connects there with a read-only API key.

    Better reading of hard files

    • Scanned PDFs and image-heavy documents go through a new OCR and parsing step, with a timeout so one slow file can’t hold up the rest.
    • Images are described as well as read, so a diagram or a photo of a whiteboard can be found by what it shows.

    Search now uses new embedding and reranking models, and processes large files in parallel. The effect is steadier ranking of the passage that actually answers the question.

    A new home for the story

    companyos.cc was rebuilt as a plain, fast static site, with this blog for field notes and dated product changes.