{
    "version": "https://jsonfeed.org/version/1",
    "title": "Argus Product Updates",
    "home_page_url": "https://argus-changelog.announcekit.app",
    "icon": "https://img.announcekit.app/ad7bdd6b086d776eaa91ed5113947955?w=150&h=50&fit=max&s=88089a118c5d13b035065cd6606aea76",
    "items": [
        {
            "id": "451748",
            "content_html": "<p>Argus now has a changelog and a help center of its own. This post says where to find them and what is in them.</p>\n<h2>Where to find them</h2>\n<ul>\n<li><strong>In Argus</strong>: open the settings menu at the foot of the sidebar. <strong>What's new</strong> opens the changelog in a panel, with a badge when there is a post you have not read. <strong>Help center</strong> opens the articles in a new tab.</li>\n<li><strong>On the web</strong>: the changelog is at <a href=\"https://announcekit.co/argus/product-updates\">announcekit.co/argus/product-updates</a> and the help center is its <a href=\"https://announcekit.co/argus/product-updates/knowledge-base\">Knowledge Base</a> tab.</li>\n<li><strong>In Slack</strong>: each new post is also sent to the Argus engineering channel.</li>\n</ul>\n<h2>The changelog</h2>\n<p>Every Friday one post covers the week. It has two parts:</p>\n<ul>\n<li><strong>Highlights</strong>: what you can now see or do in the dashboard, with screenshots.</li>\n<li><strong>Everything shipped this week</strong>: every piece of work, one line each, with the name of the person who shipped it in parentheses.</li>\n</ul>\n<p>The five weeks since the first build, from 5 October to 8 November, are already there.</p>\n<img src=\"https://img.announcekit.app/c61d1178cedd506fc57ca9aeb85689c4?s=806a1286839bfba857fbefecbfae1f44\" alt=\"The Argus changelog: weekly release notes listed by month, newest first\" />\n<h2>The help center</h2>\n<p>Fifty articles in eight folders say how each part of Argus works and where to find it:</p>\n<ul>\n<li><strong>Getting started</strong>: what Argus is, signing in, people and levels, connecting your tools.</li>\n<li><strong>Agents</strong>: agents and duties, how much an agent does on its own, testing an agent on old tickets.</li>\n<li><strong>Inbox and approvals</strong>: what waits for your OK and what approving really sends.</li>\n<li><strong>Support desk</strong>: how a conversation is handled, hand-offs, and why a reply did not go out on its own.</li>\n<li><strong>Dashboards</strong>: one article for each dashboard, from Business review to Cost.</li>\n<li><strong>Data</strong>, <strong>Office and Jarvis</strong>, and <strong>Balio team</strong>.</li>\n</ul>\n<p>The articles follow the product: each morning they are checked against what reached production the day before and corrected where a page changed.</p>\n<img src=\"https://img.announcekit.app/abcce99f6a6374f3636e4fa4895fd223?s=aa85dc731c586cec1c125bf3c074651d\" alt=\"The Argus help center: eight folders on the left and the Getting started articles on the right\" />\n<h2>Roadmap and feature requests</h2>\n<p>The same page has a <strong>Roadmap</strong> tab and a <strong>Feature Requests</strong> tab. Use <strong>Suggest Feature</strong> to send an idea, and vote on the ideas of others.</p>\n<p>Under every post you can leave a reaction or a line of feedback. Tell us what is missing.</p>",
            "url": "https://argus-changelog.announcekit.app/argus-now-has-its-own-changelog-and-help-center-31dySs",
            "title": "Argus now has its own changelog and help center",
            "summary": "Where to find Argus's changelog and help center, and what is in them.",
            "date_modified": "2026-11-12T15:10:52.038Z",
            "tags": [
                "announcement"
            ]
        },
        {
            "id": "451674",
            "content_html": "<p>This week agents became roles with a page of their own, finance got a Plan dashboard with a forecast, Balio's side was cut back to a few pages, and every change now reaches production through review and a staging step.</p>\n<h2>Highlights</h2>\n<ul>\n<li><strong>Agents</strong>: under <strong>Office</strong>, every agent is now a role with a job title, such as Customer Support Specialist or AR Specialist. One card per role, and <strong>Hire</strong> adds one. Agents outside the customer department are paused for now. (Orhan)</li>\n<li><strong>Agent page</strong>: open a card for the tabs <strong>Overview</strong>, <strong>Operations</strong>, <strong>Tests</strong>, <strong>Setup</strong>, <strong>Integrations</strong> and <strong>Activity</strong>. <strong>Mode</strong> sets how much the agent does alone: <strong>Draft</strong>, <strong>Controlled</strong>, <strong>Auto</strong> or <strong>Full</strong>. (Orhan)</li>\n<li><strong>Tests</strong>: the agent answers your closed tickets of the last 90 days. Nothing is sent. Each answer sits beside your team's real reply and gets a score. (Orhan)</li>\n</ul>\n<img src=\"https://img.announcekit.app/e1dbb5644bf2659f254457fac29f4954?s=d18d17dfcf046d5f0519c920dcf1c344\" alt=\"The Tests tab of the Customer Support Specialist: a score of 82 out of 100 on 50 old tickets, with the team's reply and the agent's answer side by side\" />\n<ul>\n<li><strong>Inbox</strong>: weekly reports no longer land here. A note nobody opened in 14 days expires, and so does a drafted reply once a person has answered the customer. (Orhan)</li>\n<li><strong>Plan</strong>: a new dashboard with <strong>Forecast</strong> and <strong>Customers</strong>. It shows actual figures, then the forecast to the end of next year. Add your own changes as drafts, and keep <strong>Notes and key dates</strong>. (Sydney)</li>\n</ul>\n<img src=\"https://img.announcekit.app/3751cf000ee336dd913d22f003f3f347?s=5222fff5510e7b94d6ba9b7b14a6de5f\" alt=\"The Plan dashboard: revenue, EBITDA and MRR outlook tiles above a chart of actual months followed by lighter forecast months\" />\n<ul>\n<li><strong>Revenue</strong> and <strong>P&amp;L</strong>: every chart has a <strong>Chart</strong> and <strong>Table</strong> switch. Click a chart to filter, and a <strong>Filtered by</strong> row names what is set. (Sydney)</li>\n<li><strong>Usage</strong>: under <strong>Product</strong>, active users, active accounts and feature adoption from your analytics tool. (Orhan)</li>\n<li><strong>Workspaces</strong>: everyone now lands here. It replaces Home, Tools, Agents, Planning, Experiments and the command palette. Each workspace opens to <strong>Overview</strong>, <strong>Integrations</strong>, <strong>Automations</strong>, <strong>Members</strong>, <strong>Usage</strong> and <strong>Controls</strong>. (Orhan)</li>\n</ul>\n<img src=\"https://img.announcekit.app/84fcf783662bf642265d185e5b950d1a?s=0335bab5f700a4c8b42710cb68a7c1ee\" alt=\"A workspace's Overview tab, What the agents changed: a chart of support metrics before and since the department's first agent\" />\n<ul>\n<li><strong>Cost</strong>: one page for agent spend across all workspaces, by workspace, agent and model. (Orhan)</li>\n</ul>\n<h2>Everything shipped this week</h2>\n<h3>Agents and automation</h3>\n<ul>\n<li><strong>Agents as roles</strong>: each agent is a role with a job title, one card per hired role, hired by role, and the old mythological names are gone (Orhan)</li>\n<li><strong>Customer roles</strong>: the customer department is now eight roles, and every hire is called by its title (Orhan)</li>\n<li><strong>Role card</strong>: the card of a role was redesigned, the summary row above the cards was removed, and roles are grouped under their teams (Orhan)</li>\n<li><strong>Agent page</strong>: one page for every agent with six tabs, a readable work queue, tools by category, the four modes Draft, Controlled, Auto and Full, and settings the engine really enforces (Orhan)</li>\n<li><strong>Tests tab</strong>: an agent can be tried on the workspace's own closed tickets before it is hired, with a score and nothing sent (Orhan)</li>\n<li><strong>Autonomy by role</strong>: one autonomy setting per role on its page, in place of one per duty (Orhan)</li>\n<li><strong>3D office</strong>: the office is now a 3D floor with one desk per role, it is the page a workspace opens on, and a desk opens the role's page (Orhan)</li>\n<li><strong>Simpler workspace menu</strong>: Today is Jarvis's chat only, and Team became <strong>Agents</strong> under <strong>Office</strong> (Orhan)</li>\n<li><strong>Customer department first</strong>: every agent outside the customer department is paused in every workspace until the customer team is designed, and nothing else about them changed (Orhan)</li>\n<li><strong>Evolution loop</strong>: each night the engine may try one tested improvement per duty and shows a card only when the result is clearly better. Built with a nightly spending cap, and the switch-on for AnnounceKit waited for the GM's OK (Orhan)</li>\n<li><strong>Onboarding run</strong>: the prove and shadow steps of a new workspace's onboarding now open and finish by themselves (Orhan)</li>\n<li><strong>Product learner</strong>: a new learner reads product events, releases and tickets to describe features, retention and how often the company ships (Orhan)</li>\n<li><strong>Organization learner</strong>: a new learner describes the team's load per department from seats, desk work and meetings, with seat details visible to the GM only (Orhan)</li>\n<li><strong>Market signals and pricing</strong>: the market learner now reads reach, hiring and news about the market each month, and a pricing suggestion is built from past price changes and competitors' prices (Orhan)</li>\n<li><strong>Learner fixes</strong>: learners keep the better of two answers instead of the newest, the Slack learner counts a stated rule as a finding and says why a run found little, and the customer learner's slowest step was made fast (Orhan)</li>\n<li><strong>Company profile freshness</strong>: each profile section carries when it was observed and until when it holds, agents are told when a section is stale, and web evidence is cached per workspace (Orhan)</li>\n<li><strong>Engine run accounting</strong>: a run reserves its budget before it starts and settles after, upkeep spend counts in the monthly limit, and a failed run is no longer read as an empty one (Orhan)</li>\n</ul>\n<h3>Inbox and approvals</h3>\n<ul>\n<li><strong>Inbox by role</strong>: the Inbox names each item by the role that made it and can be narrowed to one role (Orhan)</li>\n<li><strong>Weekly reports out of the Inbox</strong>: reports stay in the run's log, and at-risk accounts arrive as one weekly digest, with a separate card only for a VIP or critical account somebody owns (Orhan)</li>\n<li><strong>Notes expire</strong>: a note nobody read in 14 days expires, except security, VIP, refund and legal ones and those addressed to a person (Orhan)</li>\n<li><strong>Answered drafts expire</strong>: a drafted reply leaves the Inbox when the thread shows a person already answered the customer (Orhan)</li>\n<li><strong>VIP hand-offs in Slack</strong>: a VIP hand-off from any agent now also reaches its owner in Slack, tied to its Inbox item (Orhan)</li>\n<li><strong>Help center proposals</strong>: a proposed help article change is an Inbox task plus a chat post with <strong>Accept</strong> and <strong>Decline</strong>, only in a channel verified as the company's own (Orhan)</li>\n<li><strong>Decision log</strong>: explicit decisions found in stored Slack and meeting notes are logged and come back to the Inbox for review when they are due (Orhan)</li>\n<li><strong>Pause all</strong>: pausing every agent now happens in one step, and the app asks before discarding drafts that are waiting (Orhan)</li>\n<li><strong>AnnounceKit Inbox clean-up</strong>: closed, answered and superseded support items were expired from AnnounceKit's waiting Inbox, counting answers written from the shared admin account (Orhan)</li>\n</ul>\n<h3>Support desk</h3>\n<ul>\n<li><strong>Last look before sending</strong>: after the support audit of 4 Nov, a customer reply is read against the thread once more before it leaves, and a held draft goes out only on a person's decision (Orhan)</li>\n<li><strong>Holding message</strong>: AnnounceKit's \"we are on it\" message was switched off after the audit, then switched on again behind guards. It stops when a person is on the case, and its reminder note closes itself (Orhan)</li>\n<li><strong>Fact check on a second model</strong>: the check before an automatic reply can run on a different model family than the one that wrote the reply (Orhan)</li>\n<li><strong>AnnounceKit knowledge base</strong>: the desk now reads AnnounceKit's own Knowledgebase articles as help documents, and the help center keeper posts its proposals to the support channel (Orhan)</li>\n</ul>\n<h3>Dashboards</h3>\n<ul>\n<li><strong>Plan dashboard</strong>: a new dashboard in the sidebar shows the forecast beside the actuals to the end of next year, with forms where the GM enters changes and sees them in the graphs at once (Sydney)</li>\n<li><strong>Plan, Customers page</strong>: the forecast per customer and the renewals due, where opening a customer lets you change it (Sydney)</li>\n<li><strong>Drafts, notes and key dates</strong>: Plan changes can stay drafts, notes and key dates are saved on the dashboards and drawn on the charts, with alerts and an anonymous comparison with the portfolio (Sydney)</li>\n<li><strong>Chart and Table switch</strong>: every Revenue and P&amp;L chart can be read as a table (Sydney)</li>\n<li><strong>Filters</strong>: quick date ranges and <strong>Clear</strong>, a <strong>Filtered by</strong> row that names every filter set by a click, and the light theme by default (Sydney)</li>\n<li><strong>Cash flow</strong>: the Revenue cash flow page shows how customers paid, by card or by bank (Sydney)</li>\n<li><strong>P&amp;L</strong>: the P&amp;L now ends at EBITDA, and lines removed in the warehouse disappear from Argus too (Sydney)</li>\n<li><strong>Open month left out</strong>: churn lists, cohort views and customer drill-downs no longer count the month still in progress, which made them look worse than they were (Sydney)</li>\n<li><strong>Revenue charts</strong>: one axis per chart, compared periods as a dashed line, cohorts by calendar month, and the Needs attention list removed from the overview (Sydney)</li>\n<li><strong>Dashboard fixes</strong>: Past due lost the chosen date range and now keeps it, a carried-over cohort filter on Churn is now visible, and several layout faults were fixed (Sydney)</li>\n<li><strong>Plain words</strong>: the wording across Revenue, P&amp;L and Plan was rewritten in plain language (Sydney)</li>\n<li><strong>Product, Usage</strong>: a new page with active users, active accounts and feature adoption from the analytics tool's events (Orhan)</li>\n<li><strong>Business review</strong>: new <strong>Forecast</strong>, <strong>Capacity</strong> and <strong>Risks</strong> blocks: MRR, cash and churn at 30, 60 and 90 days marked reliable or not, each department's load against its capacity, and a monthly list of risks (Orhan)</li>\n<li><strong>Company goals</strong>: an admin sets goals, and each week Argus shows the pace, what drives it and a one-line explanation (Orhan)</li>\n<li><strong>Portfolio benchmark</strong>: each quarter a workspace sees its own position against anonymous portfolio figures, published only when enough workspaces report (Orhan)</li>\n<li><strong>Look and feel</strong>: a new Argus logo and colours, one icon per page, chart legends as toggles, and the app's own dropdowns everywhere (Orhan)</li>\n<li><strong>App review fixes</strong>: about thirty small faults from a review of the app were fixed, such as money shown in the workspace's currency, names in place of internal keys, and one main button per card (Orhan)</li>\n</ul>\n<h3>Data and connections</h3>\n<ul>\n<li><strong>Ahrefs</strong>: a new read-only connection that gives the market learner keyword demand, competitors' search share and visibility in AI answers, within a monthly cap (Orhan)</li>\n<li><strong>Outbound</strong>: Clay and Instantly campaigns with their full cost arrived as new Marketing pages, visible to Balio's admins only for now (Tiaan, Orhan)</li>\n<li><strong>Instantly</strong>: Instantly is now an Argus integration, and Outbound reads its Clay, Instantly and Claude keys from Integrations (Tiaan)</li>\n<li><strong>Data Report</strong>: a gap a person has accepted leaves the list and is shown apart (Orhan)</li>\n<li><strong>Switched-off connectors</strong>: a connector its owner turned off is no longer reported as a broken tool (Orhan)</li>\n<li><strong>Data quality score</strong>: the score now compares like with like across sources and splits missing contacts by cause, so it stops penalising rows that cannot be linked (Orhan)</li>\n<li><strong>One definition of paying</strong>: every part of the engine now counts a paying customer the same way, on the company's own day (Orhan)</li>\n<li><strong>Sync and retention fixes</strong>: a source with no data is retried once per period instead of being left dead, the nightly trim keeps records that others still point to, and the Slack scan keeps each channel's newest weeks (Orhan)</li>\n</ul>\n<h3>Access and security</h3>\n<ul>\n<li><strong>Security hardening</strong>: warehouse settings can be changed by Balio only, a tool connection can be finished only by the person who started it, retention settings stick, and a suspended seat loses See as (Sydney)</li>\n<li><strong>Jarvis settings</strong>: every seat keeps the Jarvis tab, and people who are not admins see only their own sections (Orhan)</li>\n<li><strong>Privacy checks</strong>: the check that personal data is covered by erasure now also looks at phone numbers, photos and links, and erasure clears photos and invoice links (Orhan)</li>\n</ul>\n<h3>Balio's side</h3>\n<ul>\n<li><strong>Workspaces</strong>: Balio's dashboard was cut back to the Workspaces list, with real tool logos, an agent cost column and no warning chips. Home, Tools, Agents and Planning are gone (Orhan)</li>\n<li><strong>Workspace page</strong>: each workspace has the tabs Overview, Integrations, Automations, Members, Usage and Controls, and Overview shows what the agents changed per department (Orhan)</li>\n<li><strong>Cost</strong>: a new page with agent spend across every workspace, by workspace, agent and model. A workspace's Usage tab no longer shows cost (Orhan)</li>\n<li><strong>Experiments removed</strong>: agents' trials were taken out of the product, and the old addresses land on Workspaces (Orhan)</li>\n<li><strong>Admin, Controls and Security</strong>: Admin and Controls got tabs and calmer tables, and Security shows its chart-led score dashboard again (Orhan)</li>\n<li><strong>Evals</strong>: Compare shows error bars and says when a difference is only noise, Calibrate takes a second labeller with export and import and has a plain-language guide, and AnnounceKit's model key now runs the calibration judges (Orhan)</li>\n</ul>\n<h3>Platform and engineering</h3>\n<ul>\n<li><strong>Every change through review</strong>: all changes now land through a pull request that a code owner approves, with a written guide and a pre-flight check for teammates (Orhan)</li>\n<li><strong>Staging before production</strong>: the working branch now deploys to a separate staging copy, and only the main branch deploys to production (Marcelo, Orhan)</li>\n<li><strong>Preview per change</strong>: each pull request can get its own preview of the dashboard, and its own backend when asked for, removed again when it closes (Marcelo, Orhan)</li>\n<li><strong>Staging secrets apart</strong>: staging reads only its own set of keys, never production's (Marcelo)</li>\n<li><strong>Merge queue and test cost</strong>: the heavy test suites run once per merged change, in a queue that tests changes one after another, which cut the test bill (Orhan)</li>\n<li><strong>Faster, steadier tests</strong>: the test run was sped up, and tests that failed only on certain days of the month or times of day were fixed (Orhan)</li>\n<li><strong>Fair scheduling</strong>: the engine's hourly upkeep jobs now take turns and are bounded, so one slow job cannot starve the others (Orhan)</li>\n<li><strong>Diagnose tools</strong>: new read-only reports for the support desk, the waiting Inbox, data quality, the learners and the sync, used to prove this week's fixes on real data (Orhan)</li>\n</ul>",
            "url": "https://argus-changelog.announcekit.app/release-notes-2-to-8-nov-agents-as-roles-a-plan-dashboard-one-workspaces-page-1Fcinm",
            "title": "Release notes, 2 to 8 Nov: agents as roles, a Plan dashboard, one Workspaces page",
            "summary": "This week agents became roles with a page of their own, finance got a Plan dashboard with a forecast, Balio's side was cut back to a few pages, and every change now reaches production through review and a staging step.",
            "date_modified": "2026-11-08T16:00:00.000Z",
            "tags": [
                "new feature"
            ]
        },
        {
            "id": "451673",
            "content_html": "<p>The busiest week so far: the workspace got a new shape (Today, Team, Data, Settings), support got its own dashboards and a full desk loop, and Argus started to learn each company from its own data.</p>\n\n<h2>Highlights</h2>\n\n<h3>Your workspace</h3>\n<ul>\n<li><strong>Today</strong> is the new landing page. <strong>This morning</strong> lists what needs a person, <strong>Waiting for you</strong> shows what is yours to decide, and you can ask <strong>Jarvis</strong> from the same page. (Orhan)</li>\n</ul>\n<img src=\"https://img.announcekit.app/daf4e2f314a9dadbdee33bc82aba0749?s=6534d6a38cbb1530fcbba8891b181cb6\" alt=\"The Today page of a sample workspace: the This morning card with six things that need a person, the Waiting for you card and the Jarvis question box.\" />\n<ul>\n<li><strong>Team</strong> brings departments, agents and their duties into one page. <strong>Hire</strong> opens a wizard that adds a duty in draft. On a duty's page, <strong>Try it on last week</strong> makes a test run that sends nothing. (Orhan)</li>\n<li><strong>Data</strong> replaces three sidebar entries with tabs: <strong>Connections</strong>, <strong>Data report</strong>, <strong>Data catalog</strong>, <strong>Company profile</strong> and <strong>Metis</strong>. The workspace admin can correct what the Company profile says. (Orhan)</li>\n</ul>\n<img src=\"https://img.announcekit.app/515a7079504948974d8536da7f37a1df?s=078e124271dacf109afe9f9963420805\" alt=\"The Data page with the Getting your data in steps and the tabs Connections, Data report, Data catalog, Company profile and Metis.\" />\n<ul>\n<li><strong>Settings</strong> is one page with the tabs <strong>General</strong>, <strong>People</strong>, <strong>Access</strong>, <strong>Budget</strong>, <strong>Notifications</strong>, <strong>Models</strong>, <strong>Mail</strong> and <strong>Privacy</strong>. <strong>What's new</strong> and <strong>Help center</strong> are in the gear menu. (Orhan)</li>\n</ul>\n\n<h3>Dashboards</h3>\n<ul>\n<li><strong>Support</strong> and <strong>Support board summary</strong> are new under <strong>Business review</strong>, and <strong>Support desk</strong> under <strong>Success</strong>. They compare your numbers with your targets and with verified benchmarks, listed under <strong>Benchmarks</strong> in Settings. (Orhan)</li>\n</ul>\n<img src=\"https://img.announcekit.app/d8ad80e662af26e98d23d79bad3a4ffb?s=128b2816d698b09f2c86289295af88e4\" alt=\"The Support dashboard: tiles for tickets resolved, first response, resolution time, CSAT, NPS and resolved by the agent, with targets, benchmarks and a created versus resolved chart.\" />\n<ul>\n<li><strong>Support insights</strong> and <strong>Research</strong> are new under <strong>Success</strong>. Insights reads closed tickets for topic, root cause and help center gaps. Research answers how a question was handled before. (Orhan)</li>\n<li><strong>Revenue</strong> has a redesigned <strong>Overview</strong> and deeper pages for <strong>MRR</strong>, <strong>Churn</strong>, <strong>Cash Flow</strong> and <strong>Past Due</strong>. <strong>P&amp;L</strong> is a new dashboard built on your management accounts. (Sydney)</li>\n</ul>\n\n<h3>Slack and connections</h3>\n<ul>\n<li><strong>Slack</strong> works both ways. Agent posts carry buttons such as approve and decline, and a reply in the thread goes to the agent. Posts to your own Slack no longer wait for approval. Anything to customers or guests still does. (Orhan)</li>\n<li><strong>Integrations</strong>: Xero connects with one sign-in, and Help Scout is no longer offered. (Orhan)</li>\n</ul>\n\n<h2>Everything shipped this week</h2>\n\n<h3>Agents and automation</h3>\n<ul>\n<li><strong>Team page</strong>: departments, agents, duties and hiring are on one page, with a page for each duty, and Engineering is a built-in desk (Orhan)</li>\n<li><strong>Hire wizard</strong>: a few questions add a duty in draft, and a member who sees a department can hire and shape its duties while none is live (Orhan)</li>\n<li><strong>Duty page</strong>: a duty reads as a procedure in one column. You can edit its steps in plain words, tell it what to change, test it on last week without sending anything, and review changes to a live duty in a working copy before publishing them (Orhan)</li>\n<li><strong>Hand-offs between agents</strong>: an agent can pass work to another agent with a deadline, and the Office shows what was handed over and what is late (Orhan)</li>\n<li><strong>Agent scorecard</strong>: each agent gets a weekly score from its results, this week against last, and the general manager gets a weekly ranking by direct message in Slack (Orhan)</li>\n<li><strong>Department mandates</strong>: each department can have a written mandate with history, set in Settings, and every agent run reads it (Orhan)</li>\n<li><strong>Autonomy guards</strong>: an agent that breaks a guard, or scores badly three days in a row, is stepped down one level on its own and never up. The ladder that would raise levels is built, not switched on (Orhan)</li>\n<li><strong>Shadow week</strong>: a duty in draft is compared each night with what the team really did, so its first week can be judged before it goes live (Orhan)</li>\n<li><strong>Company learners</strong>: Argus reads a company's support, marketing, sales, customer, finance, market and Slack history into the Company profile, and re-checks each part on a schedule. Balio runs them, they are not on a schedule of their own (Orhan)</li>\n<li><strong>Market watch</strong>: the market learner finds competitors, reads their public pricing and review pages, counts wins and losses per competitor, and marks every fact with a date after which it is checked again (Orhan)</li>\n<li><strong>Setup proposal and Setup card</strong>: from the Company profile Argus proposes the duties that fit each department, and the general manager can hire them all in draft from one page (Orhan)</li>\n<li><strong>Fact check before sending</strong>: every duty that writes to someone outside has a step that checks the draft against the facts, and the support desk passes it before a reply goes out alone (Orhan)</li>\n<li><strong>Mailbox assistant</strong>: on a person's own connected Gmail it can brief them and draft replies in their tone. Built, every part is off until its owner switches it on (Orhan)</li>\n<li><strong>Learning from edits</strong>: when a person edits or declines a draft, Argus keeps the difference and the reason, asks why in Slack after a decline, and shows the lesson to the agent on similar tickets (Orhan)</li>\n<li><strong>Working hours and holidays</strong>: business hours and public holidays follow the workspace's operating region, and a duty can run every hour at a set minute (Orhan)</li>\n</ul>\n\n<h3>Inbox and approvals</h3>\n<ul>\n<li><strong>Today</strong>: one landing page for the morning brief, what waits for you and Jarvis (Orhan)</li>\n<li><strong>Slack both ways</strong>: agent posts carry action buttons, and a reply in an agent's thread reaches that agent, which answers there (Orhan)</li>\n<li><strong>Internal Slack posts</strong>: a post to the company's own Slack is sent at every autonomy level. Shared channels, guests and customers keep the approval step (Orhan)</li>\n<li><strong>Honest counts and notifications</strong>: draft counts no longer include items that were never going to be sent, and notifications say what really waits (Orhan)</li>\n<li><strong>Drafts that go stale</strong>: a support draft is replaced when the customer writes again, and old ones are named in the morning brief (Orhan)</li>\n</ul>\n\n<h3>Support desk</h3>\n<ul>\n<li><strong>Support loop</strong>: tickets move through fixed stages with routing to the right person, bugs go to the engineering tracker, and the customer is told when the fix ships (Orhan)</li>\n<li><strong>Slack hand-off threads</strong>: a ticket that needs a person opens one Slack thread with buttons and reminders, an instruction written there is followed, and a reply from someone who is not a member becomes an Inbox draft (Orhan)</li>\n<li><strong>Desk actions</strong>: the desk can close, snooze and assign conversations on Intercom and Zendesk, each switched on per workspace. Help Scout was removed (Orhan)</li>\n<li><strong>Auto-send rules</strong>: a reply goes out alone only in categories the desk is sure of, the rule is enforced in code, and results of sent replies feed the proposal to widen it (Orhan)</li>\n<li><strong>Timers and holding messages</strong>: the desk follows up, closes quiet conversations and updates bug reporters on a timer, and can send a short holding message while a person decides. Holding messages are switched on per workspace (Orhan)</li>\n<li><strong>Ticket categories</strong>: each workspace has its own list of support categories with an editor and history, and the knowledge base agent is told when a new one is due (Orhan)</li>\n<li><strong>AnnounceKit's desk</strong>: routing, rules and the general manager's decisions of the week were applied, waiting conversations were queued again and stale drafts cleared (Orhan)</li>\n<li><strong>Research</strong>: \"how did we handle this before?\" searches past tickets, articles and internal documents from Success, Jarvis and Slack (Orhan)</li>\n<li><strong>Stored threads</strong>: conversations that were stored without their messages were filled in, tickets held in a data warehouse now carry their messages, and they count when hiring a support duty (Orhan)</li>\n</ul>\n\n<h3>Dashboards</h3>\n<ul>\n<li><strong>Support dashboards</strong>: a general manager's view, a support lead's view and a one-page board summary, on one definition of every support number, with targets and verified benchmarks (Orhan)</li>\n<li><strong>Support insights</strong>: one analysis per closed ticket (topic, root cause, help center gap), shown under Success. A fix lets a backlog resume where it stopped (Orhan)</li>\n<li><strong>Revenue overview</strong>: redesigned on the billing figures the data warehouse publishes (Sydney)</li>\n<li><strong>Revenue deep dives</strong>: MRR, Churn, Cash Flow and Past Due pages with concentration, tenure, ageing and growth (Sydney)</li>\n<li><strong>P&amp;L</strong>: a new dashboard on the management accounts. Tiles open a breakdown, and a line that moved between accounts now shows its newest value (Sydney)</li>\n<li><strong>Filters and periods</strong>: Revenue and P&amp;L filter by year, Past Due follows the date range, and Cmd or Ctrl click picks several periods (Sydney)</li>\n<li><strong>Resellers and individuals</strong>: for Fetch, resellers and individual customers are shown beside paying customers (Sydney)</li>\n<li><strong>Faster dashboards</strong>: the slowest pages (Revenue, Customers and the first load of a workspace) were sped up in the database (Orhan)</li>\n</ul>\n\n<h3>Data and connections</h3>\n<ul>\n<li><strong>Data page</strong>: Connections, Data report, Data catalog, Company profile and Metis are tabs of one page (Orhan)</li>\n<li><strong>Data report</strong>: per source, what arrived, how far back it goes, how fresh it is and what is missing. It refreshes on its own (Orhan)</li>\n<li><strong>Data catalog</strong>: every kind of record Argus holds, where it comes from, how fresh it is and which duties read it (Orhan)</li>\n<li><strong>Company profile</strong>: what Argus learned about the company, each item with its confidence and evidence, and the admin's corrections kept as versions (Orhan)</li>\n<li><strong>Metis sources and scans</strong>: Metis reads Slack history, the help center, the website and a repository's documents into memory, a scan resumes after a stop, and for Slack you choose all public channels or a list (Orhan)</li>\n<li><strong>One-click connect</strong>: a tool can be connected through its own consent screen before a pasted key, and Balio sets its app for each provider inside Argus (Orhan)</li>\n<li><strong>Xero and other connections</strong>: Xero connects by sign-in, Zendesk accepts an access token, a help center kept as files can be read, and testing a Website connection no longer fails (Orhan)</li>\n<li><strong>Marketing and sales sources</strong>: Google Ads, LinkedIn Ads, Apollo sequences and Mailgun tags can be read (Orhan)</li>\n<li><strong>Warehouse customer identity</strong>: one account per customer across billing, CRM and support for workspaces on a data warehouse, and customers an older match had merged were separated (Orhan)</li>\n<li><strong>Warehouse setup</strong>: Argus proposes the mapping that fits a warehouse and a person applies it, tools the warehouse already covers are not asked for, and syncs run after the warehouse's own rebuild (Orhan)</li>\n<li><strong>Revenue figures from the warehouse</strong>: every revenue figure is taken as the data warehouse computes it (Sydney)</li>\n<li><strong>Complete and fresh data</strong>: Argus finds gaps in history and refills them, slows down on sources that have nothing new, marks dead ones, and checks weekly that each tool still sends the fields it expects (Orhan)</li>\n<li><strong>Data quality score</strong>: each workspace has a score from counted defects and freshness, and a duty is held when the data it needs is below the mark (Orhan)</li>\n<li><strong>Reconciliation across sources</strong>: the same monthly figure is compared between billing, the warehouse and finance, and differences are explained (Orhan)</li>\n<li><strong>Identity links</strong>: Argus measures how many billing, support, product and CRM records are tied to an account and proposes the missing links for a person to confirm (Orhan)</li>\n<li><strong>Logos and photos</strong>: accounts and competitors show their logo and members their photo, without calls to outside logo services (Orhan)</li>\n<li><strong>Unit economics</strong>: gross margin, cost per customer and per plan, and a twelve month trend are added to the finance part of the Company profile (Orhan)</li>\n<li><strong>Business e-mail in the analysis</strong>: a person can share business threads from their own mailbox. Only the owner can share, and sensitive mail is dropped before it is stored (Orhan)</li>\n</ul>\n\n<h3>Access and security</h3>\n<ul>\n<li><strong>Settings</strong>: one page with tabs for General, People, Access, Budget, Notifications, Models, Mail and Privacy, in English (Orhan)</li>\n<li><strong>Access audit and hardening</strong>: an audit of who can read what led to per-person grants for sensitive data, access tiers, suspensions and a team directory, and \"See as\" never opens an inbox (Orhan)</li>\n<li><strong>AI spend visibility</strong>: spend is shown to the workspace admin and Balio's data team, and closed to members and viewers (Orhan)</li>\n<li><strong>Retention and deletion</strong>: each workspace has a retention policy, a person's data can be erased in one step, and sensitive Slack, calendar and note content is dropped before it is stored (Orhan)</li>\n<li><strong>Model keys</strong>: a workspace can bring its own keys for several AI providers under Models, and Balio's shared key stands in until it has one (Orhan)</li>\n</ul>\n\n<h3>Balio's side</h3>\n<ul>\n<li><strong>Evals</strong>: agents are tested on old tickets with test sets, several designs and models, a score against cost comparison and a review queue. AnnounceKit's first two back-tests ran (Orhan)</li>\n<li><strong>Planning by project</strong>: the plan is grouped by project (Argus or one workspace) with owners and milestones, and the old setup guide was removed (Orhan)</li>\n<li><strong>Onboarding a workspace</strong>: one command runs connect, report, learn and propose, each run is recorded step by step, and a two-day handbook and the first two pilots are written up (Orhan)</li>\n<li><strong>Due-diligence report</strong>: one page and one file with what Argus holds about a workspace, also on partial data (Orhan)</li>\n<li><strong>Engine health</strong>: a score from 0 to 100 per workspace with checks for silent failures, tasks it opens for itself, and a fallback to another model when one is down (Orhan)</li>\n<li><strong>Cost control</strong>: a cost record per run, cost per result, alerts on unusual spend, a monthly budget split across duties, cheaper models tried where quality holds, and self-repair of stuck work (Orhan)</li>\n<li><strong>Page views</strong>: page opens are recorded, so Balio can see which screens are used (Orhan)</li>\n</ul>\n\n<h3>Platform and engineering</h3>\n<ul>\n<li><strong>Visual pass</strong>: tables, Settings, the Data report, the Company profile, Metis and the Inbox were redrawn in one visual language, in light and dark (Orhan)</li>\n<li><strong>What's new and Help center</strong>: both open from the gear menu, with an unread count on What's new (Orhan)</li>\n<li><strong>Faster, safer releases</strong>: the test suite runs once per release instead of three times, tests are chosen from what changed, flaky timing tests were fixed, and a new guard stops a database change from undoing an earlier one (Orhan)</li>\n<li><strong>Diagnose tools</strong>: dozens of read-only checks were added for support, evals, the warehouse, access and the database, so a question about production is answered from data (Orhan)</li>\n</ul>",
            "url": "https://argus-changelog.announcekit.app/release-notes-26-oct-to-1-nov-today-team-and-data-pages-support-dashboards-the-company-learners-1E3TR6",
            "title": "Release notes, 26 Oct to 1 Nov: Today, Team and Data pages, support dashboards, the company learners",
            "summary": "The busiest week so far: the workspace got a new shape (Today, Team, Data, Settings), support got its own dashboards and a full desk loop, and Argus started to learn each company from its own data.",
            "date_modified": "2026-11-01T16:00:00.000Z",
            "tags": [
                "new feature"
            ]
        },
        {
            "id": "451672",
            "content_html": "<p>This week the Balio team got its own side of Argus, with a Home page, a plan and trials for agents, and workspace dashboards can now be read one channel at a time.</p>\n\n<h2>Highlights</h2>\n<ul>\n<li><strong>Home</strong>: the Balio team's new landing page shows what needs Balio now across every workspace: broken tools, late tasks, trials ready to decide and security fixes. <strong>Tools</strong> and <strong>Agents</strong> list every tool and agent, and <strong>Search Foundry</strong> finds any of them (Orhan)</li>\n</ul>\n<img src=\"https://img.announcekit.app/0f803c25f169ed64d287c994e2471426?s=ef45626ae0812689e9ee98bcb4f627e6\" alt=\"The Foundry Home page with the Needs Balio tiles, workspaces in build, tools and experiments\" />\n<ul>\n<li><strong>Experiments</strong>: every agent on trial, measured against the weeks before it was switched on. A trial marked <strong>Ready to go live</strong> waits for a person to decide (Orhan)</li>\n</ul>\n<img src=\"https://img.announcekit.app/ca8c2560e9c78705b49c207fd877df9a?s=19c372d4bd84e31fac4ce3ec36b547fd\" alt=\"The Experiments page with trial cards showing median first response before and after, and one trial ready to go live\" />\n<ul>\n<li><strong>Planning</strong>: the Balio team's plan in six views: <strong>Cockpit</strong>, <strong>Workspaces</strong>, <strong>Timeline</strong>, <strong>Tasks</strong>, <strong>Review</strong> and <strong>Team</strong>. A workspace's <strong>Setup</strong> tab starts its plan from a template and a target go-live date (Orhan)</li>\n<li><strong>Workspaces</strong>: one dashboard lists every workspace, each with its own admin page. The new <strong>Data map</strong> tab draws the tools a workspace uses and what flows between them (Orhan)</li>\n<li><strong>Security</strong>: a console with a score, the checks that passed and the ones to fix or look at (Orhan)</li>\n<li><strong>Channel filter</strong>: on <strong>Revenue</strong>, <strong>Success</strong> and <strong>Customers</strong>, pick a channel or a partner to see only the customers who came through it. <strong>Growth</strong>, <strong>Channels</strong> now draws revenue and customers by channel (Orhan)</li>\n</ul>\n<img src=\"https://img.announcekit.app/89a7540a92f42a044424fea99797bf3f?s=b8f89e8a2bd93427057b4fa979af5a56\" alt=\"The Revenue dashboard with the channel filter in the header set to All partners\" />\n<ul>\n<li><strong>Team &amp; hiring</strong>: 18 new duties to hire, among them renewals, MRR bridge, pull request review and board update. None switches on by itself, and each starts in draft (Orhan)</li>\n<li><strong>Support</strong>: every workspace now runs the same support flow. The agent can leave its suggested reply as an internal note on the ticket, and ticket categories come from your own tickets (Orhan)</li>\n<li><strong>Logs</strong>: Reports is now <strong>Logs</strong> under <strong>Agents</strong>, for admins. Tone and agent rules moved from Settings to <strong>Metis</strong> (Orhan)</li>\n</ul>\n\n<h2>Everything shipped this week</h2>\n\n<h3>Agents and automation</h3>\n<ul>\n<li><strong>Experiments</strong>: an agent switched on in draft now runs as a trial, measured against the weeks before it, with a board, a read-out per trial, a check that says when it is ready to go live, and a way to start a trial by hand (Orhan)</li>\n<li><strong>Hireable-only duties</strong>: a plan for 18 new duties, and a rule that a new duty is offered in Team &amp; hiring but never switched on by a hire, so adding one changes nothing until a person turns it on (Orhan)</li>\n<li><strong>Customer health duties</strong>: support health check, churn intake, renewals and expansion signals can be hired; built, not switched on (Orhan)</li>\n<li><strong>Finance close duties</strong>: MRR bridge, cash review and past-due review can be hired; built, not switched on (Orhan)</li>\n<li><strong>Growth strategy duties</strong>: a competitor scorecard, a growth report and an outbound strategy among them can be hired; built, not switched on (Orhan)</li>\n<li><strong>Engineering desk duties</strong>: pull request review (quiet on weekends), weekly code review, engineering report and QA test plan can be hired; built, not switched on (Orhan)</li>\n<li><strong>Operations and executive duties</strong>: sync health, workforce review and board update can be hired; built, not switched on (Orhan)</li>\n<li><strong>Agent page and Logs</strong>: the agent page has one header with an action bar and each duty's status as plain labels, and Reports became Logs under Agents, for admins (Orhan)</li>\n<li><strong>Agent runner</strong>: the runner now stops cleanly when a new version is deployed, and the data sync is no longer listed as an agent (Orhan)</li>\n</ul>\n\n<h3>Support desk</h3>\n<ul>\n<li><strong>One support flow</strong>: every workspace runs the same support flow, stage by stage, instead of a setup of its own (Orhan)</li>\n<li><strong>Desk notes</strong>: the agent can leave its suggested reply as an internal note on the ticket, written as a named teammate, reading the whole ticket and building on the team's answer; switched on for Fetch and AnnounceKit (Orhan)</li>\n<li><strong>Loop builder</strong>: steps are numbered, a stage can take any of the desk's duties or \"No one yet (plan only)\", and missing items are named (Orhan)</li>\n<li><strong>Ticket categories</strong>: support categories are now derived from a workspace's own tickets, never typed in by hand; two changes to the code the agents read were held back until the general manager approves them (Orhan)</li>\n</ul>\n\n<h3>Dashboards</h3>\n<ul>\n<li><strong>Channel filter</strong>: Revenue, Success and Customers can be filtered to one channel or one partner, the choice is remembered between those pages, and the page keeps the last numbers on screen while a new filter loads (Orhan)</li>\n<li><strong>Growth, Channels</strong>: the page draws revenue and customers by channel with partners, and the coverage strip moved off the dashboards into an information button for admins (Orhan)</li>\n<li><strong>Shared bills</strong>: a bill recorded as shared between partners is split across them in the Growth numbers, first used for Fetch (Orhan)</li>\n<li><strong>Billed through a partner</strong>: Fetch's hotels count as its customers and the systems that bill them as billing partners, with a badge on the customer's page (Orhan)</li>\n<li><strong>Faster Growth pages</strong>: the content block was reading far more search data than it needed, which made the page slow; it now reads only its own pages (Orhan)</li>\n<li><strong>Faster Revenue pages</strong>: the Revenue read and the nightly metrics were slow on large accounts; both were reworked after timing every dashboard read in production (Orhan)</li>\n<li><strong>Settings</strong>: tone, hand-offs, agent rules, customer fields and the growth profile are now set in Metis only, not twice (Orhan)</li>\n<li><strong>Team table</strong>: the actions fit on one line and long department names wrap inside their column (Orhan)</li>\n<li><strong>Sidebar</strong>: the \"new\" badge beside dashboards is gone (Orhan)</li>\n</ul>\n\n<h3>Data and connections</h3>\n<ul>\n<li><strong>Empty warehouse</strong>: a warehouse connection that imports nothing used to show as healthy; it is now flagged (Orhan)</li>\n</ul>\n\n<h3>Access and security</h3>\n<ul>\n<li><strong>Sign-in</strong>: after Continue with Google some people landed on \"You are not signed in\"; that detour is fixed, and a refused sign-in now shows its reason (Orhan)</li>\n<li><strong>Security console</strong>: a page for Balio admins with a score and every check, including that sign-in is Google only (Orhan)</li>\n<li><strong>Weekly security check</strong>: a routine that scans the code and audits the database without changing anything, and feeds the console (Orhan)</li>\n<li><strong>Read-only login for the data engineer</strong>: a database login that can read and cannot change anything (Orhan)</li>\n<li><strong>The data team reaches the plan</strong>: the data team can open and work Planning and a workspace's setup steps, and nothing else on Balio's side (Orhan)</li>\n</ul>\n\n<h3>Balio's side</h3>\n<ul>\n<li><strong>Workspaces</strong>: one dashboard for every workspace with first and last seen for its people, and a simpler admin page per workspace (Orhan)</li>\n<li><strong>Planning</strong>: the Balio team's one plan to the end of the year, with workspaces as projects, checklists read live from each workspace's data, a week and month calendar and a timeline with milestones (Orhan)</li>\n<li><strong>Setup guide</strong>: a workspace's Setup tab plans every step from kickoff to go-live from a template, opens the next steps as earlier ones close, and starts when the workspace is created (Orhan)</li>\n<li><strong>Planning cockpit</strong>: one lane per role with what is ready, late and waiting on someone, the week's load, a weekly review and a team view (Orhan)</li>\n<li><strong>Four setup roles</strong>: setup steps are owned by chief of staff, forward deployed engineer, data engineer and product lead (Orhan)</li>\n<li><strong>Planning opens faster</strong>: the page was slow to appear; it now shows at once and fills in the live facts after (Orhan)</li>\n<li><strong>Home and search</strong>: a Home page with what needs Balio now, a new sidebar with counts, tabs on every workspace's admin page, and search across workspaces, tools and agents (Orhan)</li>\n<li><strong>Tools and Agents</strong>: a page for every tool with where it is connected and whether it works, a page for every agent across workspaces, and a Tools tab on each workspace (Orhan)</li>\n<li><strong>Tool watch</strong>: a broken tool opens a task on the plan for the right role and closes it when the tool works again (Orhan)</li>\n<li><strong>Data map</strong>: a drawing of each workspace's tools and what flows between them, suggested from its connections and editable; it changes no connection (Orhan)</li>\n<li><strong>Team photos</strong>: profile photos for the Balio team on Planning (Orhan)</li>\n</ul>\n\n<h3>Platform and engineering</h3>\n<ul>\n<li><strong>Database load</strong>: the busiest lookups got indexes, the business review refreshes only when it is out of date and the upkeep runs once a minute, measured before and after on production (Orhan)</li>\n<li><strong>Schema snapshot</strong>: the stored picture of the database no longer changes with the version of the tool that writes it (Orhan)</li>\n<li><strong>Local test database</strong>: one script starts the local database the test suite needs (Orhan)</li>\n<li><strong>Test fixes</strong>: three tests that failed for reasons unrelated to the product were fixed, among them a baseline check that broke on a database without Fetch (Orhan)</li>\n<li><strong>Diagnose tools</strong>: read-only reports for the last applied database changes, the support desk's notes, why a company's code cannot be read, and the setup audit (Orhan)</li>\n</ul>",
            "url": "https://argus-changelog.announcekit.app/release-notes-19-to-25-oct-foundry-home-experiments-a-channel-filter-on-dashboards-1CVvkQ",
            "title": "Release notes, 19 to 25 Oct: Foundry Home, Experiments, a channel filter on dashboards",
            "summary": "This week the Balio team got its own side of Argus, with a Home page, a plan and trials for agents, and workspace dashboards can now be read one channel at a time.",
            "date_modified": "2026-10-25T16:00:00.000Z",
            "tags": [
                "new feature"
            ]
        },
        {
            "id": "451671",
            "content_html": "<p>The first workspace went live on Argus this week, and the dashboard grew around it: an office for the agents, a Business review, a clearer Inbox, and access by department.</p>\n\n<h2>Highlights</h2>\n<ul>\n  <li><strong>Office</strong>: every workspace now opens on an office floor. Each desk shows what its agent is doing, the <strong>Needs you</strong> card counts what waits for you, and <strong>Open inbox</strong> takes you there. <strong>Full screen</strong> shows the floor alone (Orhan)</li>\n</ul>\n<img src=\"https://img.announcekit.app/81fd83653f4972d7be51b8df2c566370?s=c9ea5d346b1038554fd03bacc35ec8be\" alt=\"The Office view of a sample workspace: the Needs you card with 33 items waiting, tasks done this week, and the office floor with the folders waiting on the general manager.\" />\n<ul>\n  <li><strong>Inbox</strong>: each card says what approving does, such as <strong>Sends an e-mail</strong> or <strong>Posts on Slack</strong>, with a <strong>Why</strong> line and a <strong>What happens</strong> section. You can approve, edit, dismiss, put a card aside for later, or hand it to a colleague with <strong>Assign to</strong>. Anything that leaves the company asks you to confirm first (Orhan)</li>\n</ul>\n<img src=\"https://img.announcekit.app/dd453f1a16951fadb806306583f0ae7a?s=09428b15bb15347f268648b7d8dd05a6\" alt=\"The Inbox with a drafted e-mail reply: the Sends an e-mail label, the Why line, the full message, and the buttons to approve, edit, dismiss, put aside or assign.\" />\n<ul>\n  <li><strong>Agents</strong>: one employee per department, each with its own duties and a name such as Atlas or Hermes. An agent's page shows its goals with the current value (Orhan)</li>\n  <li><strong>Reports</strong>: one readable report per agent run. Agents' summaries now live here, so the Inbox and Slack carry only actions (Orhan)</li>\n  <li><strong>Business review</strong>: the monthly and quarterly review numbers on one page, with targets, a <strong>Gaps</strong> tab that names what is missing, and <strong>Download deck</strong> for the QBR or MBR as a PowerPoint file (Orhan)</li>\n</ul>\n<img src=\"https://img.announcekit.app/e71b9058bddb93f81d884f16e91bd624?s=f28ac04ee00aaa29fde536b06fd0a9c3\" alt=\"The Business review page of a sample workspace: MRR, ARR, revenue and margin tiles, the Targets hit rings, and the Download deck button.\" />\n<ul>\n  <li><strong>Growth</strong>: the <strong>Overview</strong> page answers where growth comes from, starting with <strong>Revenue by channel</strong> (Orhan)</li>\n  <li><strong>Team</strong>: in <strong>Settings</strong>, give each person the departments they work in and a level for each: <strong>Sees</strong>, <strong>Decides</strong> or <strong>Manages</strong>. Admins can use <strong>See as</strong> to open the workspace as that person (Orhan)</li>\n  <li><strong>Metis</strong>: the knowledge page is now your company's brain. It shows what every agent knows and follows, and which questions are still running on safe defaults (Orhan)</li>\n</ul>\n\n<h2>Everything shipped this week</h2>\n\n<h3>Agents and automation</h3>\n<ul>\n  <li><strong>AnnounceKit live on Argus</strong>: AnnounceKit's agents moved to Argus in draft mode, with Argus's own customer records and the website as sources, so every outward step waits for approval (Orhan)</li>\n  <li><strong>Office floor</strong>: an office drawn in department zones where each desk shows its agent's real state, with a clock, a weather chip, full screen and a card for what needs you (Orhan)</li>\n  <li><strong>Office as the landing page</strong>: a workspace opens on the Office, the old Home page is gone, and a person with one workspace starts inside it (Orhan)</li>\n  <li><strong>3D office and walk</strong>: a 3D version of the office and a walk across the floor for the general manager were built, with a switch between the flat and the 3D view (Orhan)</li>\n  <li><strong>One employee per department</strong>: agents are grouped as one virtual employee per department with its duties, named after mythological figures, and a duty can read its colleagues' last runs (Orhan)</li>\n  <li><strong>Agent goals</strong>: each agent can carry a goal with a baseline, a target and an owner, and its page shows the current value (Orhan)</li>\n  <li><strong>Reports page</strong>: one readable report per run with filters, and agents' summaries moved out of the Inbox and Slack (Orhan)</li>\n  <li><strong>Slack threads</strong>: an agent's posts in a channel now sit in one thread per agent, channel and week (Orhan)</li>\n  <li><strong>Workflows</strong>: nine templated loops that a general manager can read, tune and build from scratch in a workflow editor, with the story, the flow and the history (Orhan)</li>\n  <li><strong>Content pipeline</strong>: the marketing agents hand work to each other as cases, the general manager decides both approvals, and Argus never merges a change itself (Orhan)</li>\n  <li><strong>Weekly update and partner report</strong>: two new reporting duties that deliver a report with e-mail copies, and a monthly digest that compares periods (Orhan)</li>\n  <li><strong>Product loops</strong>: the feedback, release notes, roadmap and competitor duties read more sources and their four templates went live (Orhan)</li>\n  <li><strong>Sales flows</strong>: the ideal customer profile is drawn from paying customers, with lead research and campaigns that learn from results (Orhan)</li>\n  <li><strong>Overdue invoices</strong>: chasing became a sequence of reminders that carry the billing system's own payment link (Orhan)</li>\n  <li><strong>Jarvis</strong>: powers per person, approvals inside the conversation, a web reader and video, and a voice workspace with panes (Orhan)</li>\n  <li><strong>Company brain</strong>: Metis keeps answers, uploads, customer memories and an operating brief for the agents. The duty that maintains it is built, not switched on (Orhan)</li>\n  <li><strong>Fetch's first agents</strong>: a support agent and a product manager were hired for Fetch in draft mode, from a plan based on its tickets, code and tools (Orhan)</li>\n  <li><strong>Failed runs clear</strong>: a failed run leaves the list once the agent has run well again (Orhan)</li>\n</ul>\n\n<h3>Inbox and approvals</h3>\n<ul>\n  <li><strong>What approving does</strong>: each approval says where it goes, how it is sent and why, in one layout per route and without internal ids (Orhan)</li>\n  <li><strong>Hand to a colleague</strong>: an approval can be assigned to someone else with a note, and notes from colleagues arrive as Inbox cards (Orhan)</li>\n  <li><strong>Personal list</strong>: the Inbox shows what waits on you, with Dismiss and a reminder for later (Orhan)</li>\n  <li><strong>Notification center</strong>: a full width Inbox with one tab group, icon actions with keys, filters by type and agent, and a confirm step before anything leaves the company (Orhan)</li>\n  <li><strong>Fewer cards</strong>: notes are kept apart from decisions, one digest per agent and topic a day, one card for a run's issues, stale drafts expire, and low-value hand-offs are grouped (Orhan)</li>\n  <li><strong>One waiting count</strong>: the number of things waiting on you is the same on every page (Orhan)</li>\n</ul>\n\n<h3>Support desk</h3>\n<ul>\n  <li><strong>Answers from the code</strong>: the support agent can read the product's code through GitHub and search the knowledge base, which keeps its headings and links (Orhan)</li>\n  <li><strong>A draft for every ticket</strong>: the support agent can draft a reply to every ticket, mark the ones that need review and record hand-offs as taken (Orhan)</li>\n  <li><strong>Help center drafts</strong>: the knowledge base agent creates new Zendesk Guide articles as drafts only, and proposes articles for the gaps support found (Orhan)</li>\n</ul>\n\n<h3>Dashboards</h3>\n<ul>\n  <li><strong>Business review</strong>: the review numbers as the first dashboard, drawn as charts and target rings, each with its status and gap, with finance's figures from the last closed month (Orhan)</li>\n  <li><strong>Business review speed</strong>: the page timed out on large workspaces. It now reads a stored copy that is kept fresh (Orhan)</li>\n  <li><strong>Review deck</strong>: the QBR or MBR pack downloads as a PowerPoint file in one click, with a forecast and a growth levers slide (Orhan)</li>\n  <li><strong>Growth by channel</strong>: eleven channels, a growth profile, question blocks on Growth, channel filters on Customers, and how each customer got here on its page (Orhan)</li>\n  <li><strong>Partner channels</strong>: Growth shows channel-partner metrics from the deals, and Fetch's partners were recorded from its import sheet (Orhan)</li>\n  <li><strong>Customer records</strong>: tags, categories, member notes, links between records of the same customer, and a setting for customer fields (Orhan)</li>\n  <li><strong>Honest dashboards</strong>: a dashboard with no data is locked instead of empty, empty tiles say Coming soon, illustrative blocks say Sample data (Orhan)</li>\n  <li><strong>Where a number comes from</strong>: a tip beside every number names its source and its last sync (Orhan)</li>\n  <li><strong>Pipeline and deals</strong>: the pipeline follows the CRM, a signed deal counts as won only once the customer has paid, and deals get a reliable open date (Orhan)</li>\n  <li><strong>Fetch's dashboards</strong>: Growth, Churn, Cash flow and Reconciliation were prepared for Fetch's demo, with its review cards as the data team reviewed them (Orhan)</li>\n  <li><strong>Plain words and phones</strong>: a wording pass on the office, inbox, workflow and agent pages, filters that fold on a phone, and one style of selects and tabs (Orhan)</li>\n</ul>\n\n<h3>Data and connections</h3>\n<ul>\n  <li><strong>Integrations page</strong>: tools in use are shown in fitting categories, with a row per dashboard for what your tools feed (Orhan)</li>\n  <li><strong>Connections that need you</strong>: a connection whose key was rejected says so and waits for its owner instead of failing every sync (Orhan)</li>\n  <li><strong>Mailgun</strong>: each sending domain has its own key, with a separate one for outreach, and errors say Mailgun's own reason (Orhan)</li>\n  <li><strong>Fetch's warehouse</strong>: Fetch's Snowflake views are read through a reviewed mapping, its management accounts become the booked P&amp;L, and its tickets come from Zendesk directly (Orhan)</li>\n  <li><strong>Warehouse sync</strong>: rows the warehouse dropped are removed, a changed mapping is read again, and a warehouse that delivers billing counts as billing (Orhan)</li>\n  <li><strong>Paddle fixes</strong>: an unsent Paddle transaction was counted as an open invoice and recurring discounts were missing from MRR. Both are fixed, and paid invoices carry their paid date (Orhan)</li>\n  <li><strong>Receivables</strong>: open receivables count only what was billed and is still owed (Orhan)</li>\n  <li><strong>AnnounceKit's review data</strong>: the 2026 budget and actuals were loaded and the pipeline was cleaned up for the quarterly review (Orhan)</li>\n  <li><strong>Time zones</strong>: changing a workspace's time zone recomputes its metric history (Orhan)</li>\n  <li><strong>Meetings and mail</strong>: internal participants no longer decide which customer a meeting or mail thread belongs to (Orhan)</li>\n  <li><strong>Code check</strong>: a read-only check lists the third-party tools a company's code uses, through its GitHub connection (Orhan)</li>\n</ul>\n\n<h3>Access and security</h3>\n<ul>\n  <li><strong>Roles</strong>: an owner, a read-only Balio reviewer, a Balio data team role and a workspace member role, with roles kept as data (Orhan)</li>\n  <li><strong>Departments and levels</strong>: workspace access is given per department at three levels, least privilege by default, edited in one Team grid (Orhan)</li>\n  <li><strong>See as</strong>: a workspace admin can open the workspace as one of its seats for a limited time (Orhan)</li>\n  <li><strong>Only what you may use</strong>: pages, metrics, inbox actions and connections a person cannot use are hidden (Orhan)</li>\n  <li><strong>Sensitive figures</strong>: AI spend is shown to workspace admins and Balio only, and an account's billing in Customers sits behind a switch (Orhan)</li>\n  <li><strong>Privacy</strong>: a path to erase a person's data, retention rules, and no card data kept in billing records (Orhan)</li>\n</ul>\n\n<h3>Balio's side</h3>\n<ul>\n  <li><strong>Workspace readiness</strong>: Foundry scores how ready each workspace is, from a workforce model of 29 roles and what each workflow needs (Orhan)</li>\n  <li><strong>New workspace in one step</strong>: creating a workspace takes one step and the rest moves to Getting started (Orhan)</li>\n  <li><strong>Workspace controls</strong>: tables for modules and data sets, hireable agents, a monthly limit and finance plans (Orhan)</li>\n  <li><strong>Health page</strong>: Foundry shows whether the runner is alive, and a sync is flagged stale after two hours (Orhan)</li>\n  <li><strong>Company-specific behaviour</strong>: an audit found where Argus behaved differently per company, and five packages turned those cases into settings (Orhan)</li>\n</ul>\n\n<h3>Platform and engineering</h3>\n<ul>\n  <li><strong>Database changes</strong>: the schema is kept as a reviewable tree with safer change checks, and access checks are answered once per statement (Orhan)</li>\n  <li><strong>Tests</strong>: runtime tests run in isolation, a missing database call is a visible error, and the evals gained a second made-up company (Orhan)</li>\n  <li><strong>Diagnose tools</strong>: new read-only checks for support, revenue, approvals, the Business review, connections and Fetch's data (Orhan)</li>\n  <li><strong>Reload on a new release</strong>: an open tab reloads once when it asks for files of an older release (Orhan)</li>\n</ul>",
            "url": "https://argus-changelog.announcekit.app/release-notes-12-to-18-oct-the-office-business-review-a-clearer-inbox-1BN6OA",
            "title": "Release notes, 12 to 18 Oct: the Office, Business review, a clearer Inbox",
            "summary": "The first workspace went live on Argus this week, and the dashboard grew around it: an office for the agents, a Business review, a clearer Inbox, and access by department.",
            "date_modified": "2026-10-18T16:00:00.000Z",
            "tags": [
                "new feature"
            ]
        },
        {
            "id": "451670",
            "content_html": "<p>The first week of Argus: one workspace per company, where agents do the routine work, people approve what goes out, and the company's numbers sit on one set of dashboards.</p>\n<h2>Highlights</h2>\n<ul>\n<li><strong>Agents</strong>: your agents sit on a floor by department, with what each is doing and what needs you. <strong>Org chart</strong> shows who reports to whom. <strong>Hire agents</strong> lists 17 agents across Sales, Customer Success, Finance, Marketing and Product. A hired agent starts in draft and sends nothing on its own. (Orhan)</li>\n</ul>\n<img src=\"https://img.announcekit.app/703b7e414eff848cb7271b15daf2daf2?s=634935d10bbbd9106c9242c2aedc75b9\" alt=\"The Agents page: 26 items waiting for an OK, four reports on your desk, and agents grouped by department on the floor\" />\n<ul>\n<li><strong>Inbox</strong>: every e-mail, reply or post an agent wants to send waits here. Read it, then <strong>Approve</strong>, <strong>Edit</strong> or <strong>Skip</strong>. Filter by type or by agent. (Orhan)</li>\n</ul>\n<img src=\"https://img.announcekit.app/3038a34f2959f2727c468b7a99065d97?s=c524052a897569801c881d26cbdd2461\" alt=\"The Inbox: a Slack post drafted by the Support desk agent, with Approve, Edit and Skip buttons\" />\n<ul>\n<li><strong>Jarvis</strong>: ask a question about your company and get the answer with its numbers. Open it from the sidebar or with Ctrl K on any page. Once connected, it also answers in Slack and Telegram. (Orhan)</li>\n<li><strong>Home</strong>: the main numbers, your calendar today, mail awaiting your reply, your tasks and the morning brief. (Orhan)</li>\n<li><strong>Dashboards</strong>: <strong>Revenue</strong>, <strong>Customers</strong>, <strong>Success</strong>, <strong>Growth</strong>, <strong>Marketing</strong>, <strong>Product</strong>, <strong>Cost</strong> and <strong>Monthly review</strong>, filled from your connected tools. (Orhan)</li>\n</ul>\n<img src=\"https://img.announcekit.app/032a62e0cd6590c95e6e64b9436146ad?s=831a11cde41c916061cab2af0ce3fd97\" alt=\"The Home page: six headline numbers, today's calendar, mail awaiting a reply, tasks and free days next week\" />\n<ul>\n<li><strong>Customers</strong>: one record per account with billing, product use and support together. <strong>Review matches</strong> lists possible duplicates for you to confirm. (Orhan)</li>\n<li><strong>Board</strong>: a product board under <strong>Product</strong> that takes in Linear issues. <strong>Send to Linear</strong> waits for your approval first. (Orhan)</li>\n<li><strong>Integrations</strong>: connect billing, support, analytics and other tools. A tool syncs when you connect it, then every hour. (Orhan)</li>\n<li><strong>Knowledge</strong>: the help articles, website pages and company notes your agents read before they answer. (Orhan)</li>\n</ul>\n<h2>Everything shipped this week</h2>\n<h3>Agents and automation</h3>\n<ul>\n<li><strong>Agents floor</strong>: a page that shows every agent at a desk in its department, what it is doing now and what waits for you (Orhan)</li>\n<li><strong>Departments, Org chart and hiring</strong>: agents have roles and departments, you can hire into an open seat or let an agent go, and department heads send their reports up to the general manager (Orhan)</li>\n<li><strong>A roster of 17 agents</strong>: agents for support, collections, sales, customer success, marketing, product and finance, all written to one standard that says what each reads, what it may decide and when it hands over to a person (Orhan)</li>\n<li><strong>Hire agents</strong>: a catalogue where each agent card shows the tools it needs, its tasks and its monthly cost, with one button to hire it in draft (Orhan)</li>\n<li><strong>How it works</strong>: each agent's page draws its work as a flow, from what starts it to what it reads, decides and sends (Orhan)</li>\n<li><strong>Tell the agent and sources consulted</strong>: you can leave an instruction for an agent, and each run lists the sources the agent read before it answered (Orhan)</li>\n<li><strong>Autonomy levels</strong>: each agent has a level that sets what it may send without asking, with a record of every change and a weekly scorecard (Orhan)</li>\n<li><strong>Company memory and hand-offs</strong>: agents share what they learn, pass work to each other, and a Team manager agent reviews their reports and proposes improvements (Orhan)</li>\n<li><strong>Six routine agents for any company</strong>: six more agents that do not depend on one company's setup, with a table that shows what each still needs before it can start (Orhan)</li>\n<li><strong>Jarvis</strong>: an assistant for the general manager that answers questions about the company from its data, on its own page and from a Ctrl K bar on every page (Orhan)</li>\n<li><strong>Jarvis memory and web search</strong>: Jarvis remembers what you ask it to keep, forgets on request, and can search the web and list its sources (Orhan)</li>\n<li><strong>Jarvis in Slack</strong>: a direct message or a mention of Argus in Slack gets Jarvis's answer in the same thread (Orhan)</li>\n<li><strong>Jarvis in Telegram</strong>: link your Telegram account in Settings and ask Jarvis there, by text or by voice note, and approve items from the chat (Orhan)</li>\n<li><strong>Jarvis voice</strong>: hold to talk to Jarvis and hear the answer, with a voice mode that works over any company page (Orhan)</li>\n<li><strong>Jarvis calendar and mail actions</strong>: Jarvis can prepare a calendar event or an e-mail for you, and it goes out only after you approve it (Orhan)</li>\n<li><strong>Jarvis watch and settings</strong>: Jarvis checks the company every hour and nudges you about what needs attention, within the permissions and standing orders you set in Settings (Orhan)</li>\n<li><strong>Morning brief per person</strong>: the morning brief now goes to each recipient as a direct message with their own day, next to the channel post (Orhan)</li>\n<li><strong>Agents on the company's own AI key</strong>: each company's agents run on that company's key, and Argus can now route work to several AI providers and to cheaper models where they do (Orhan)</li>\n<li><strong>Agent reply fixes</strong>: replies signed with a team name are no longer rejected, and a reply that was cut off at the length limit is asked for again in smaller pieces (Orhan)</li>\n<li><strong>Health score fixes</strong>: the health agent scores every paying account in one pass and no longer marks an account at risk only because its product use is not tracked (Orhan)</li>\n<li><strong>Event triggers</strong>: the groundwork for agents that start when something happens, such as a new case, and not only on a schedule (Orhan)</li>\n<li><strong>Agent test cases</strong>: every agent has a set of written cases it must pass, including refusals, spending limits and attempts to mislead it (Orhan)</li>\n</ul>\n<h3>Inbox and approvals</h3>\n<ul>\n<li><strong>Inbox</strong>: everything an agent wants to send waits in one list in plain language, with Approve, Edit and Skip and filters by type and agent (Orhan)</li>\n<li><strong>Approved actions go out through your own tools</strong>: an approved e-mail, reply or post is sent from the company's own mailbox, help desk or chat (Orhan)</li>\n<li><strong>Nothing live by default</strong>: a newly hired agent only drafts until someone switches it to live (Orhan)</li>\n<li><strong>Each send goes out once</strong>: an approved item can no longer be sent twice, and each company has its own send queue so one busy company does not delay another (Orhan)</li>\n<li><strong>Sender roles</strong>: agents send as billing, success, outreach or internal, each from the address you set (Orhan)</li>\n<li><strong>Agents' own e-mails go to known people</strong>: an agent's reports go only to people listed for the workspace, and Settings has a list of who receives them (Orhan)</li>\n</ul>\n<h3>Support desk</h3>\n<ul>\n<li><strong>Support desk agent</strong>: the support agent now looks up the customer and the help articles before it drafts, and hands over to a person when the topic is outside what it may decide (Orhan)</li>\n<li><strong>People and escalation</strong>: Settings lists your people, which topics go to whom, and the rules a reply must follow (Orhan)</li>\n</ul>\n<h3>Dashboards</h3>\n<ul>\n<li><strong>Home</strong>: a first page with the headline numbers, today's calendar, mail awaiting your reply, your tasks, free days and the morning brief (Orhan)</li>\n<li><strong>Dashboards on real data</strong>: Revenue, Success, Growth, Marketing, Product, Cost and Monthly review read from the connected tools, in the company's reporting currency, and a block with no data says so (Orhan)</li>\n<li><strong>Customers and the customer page</strong>: a list of every account by segment, and one page per customer with overview, billing, product use, support and contacts (Orhan)</li>\n<li><strong>Review matches</strong>: records of the same customer from different tools are joined into one account, and uncertain matches wait for a person to confirm (Orhan)</li>\n<li><strong>Product board</strong>: a board per company that takes in Linear issues and GitHub pull requests, shows agent suggestions, and sends a card to Linear after approval (Orhan)</li>\n<li><strong>Pipeline board and Funnels</strong>: two working pages under Growth for deals by stage and for conversion step by step (Orhan)</li>\n<li><strong>Cost and Monthly review books</strong>: Cost gains an Invoiced page and Monthly review an Actuals page, and a general manager can edit the books, budget and vendor terms (Orhan)</li>\n<li><strong>Agent results on pages</strong>: what agents produce, such as health tiers, the roadmap check, release notes, competitor notes and outbound drafts, appears on the matching dashboard page (Orhan)</li>\n<li><strong>Churn, sign-ups and traffic detail</strong>: churn cases with reasons, live sign-ups with their channel, search position, countries and visits sent by AI assistants (Orhan)</li>\n<li><strong>Meetings matched to customers</strong>: calendar and meeting-note entries are matched to customers by the attendees' e-mail addresses (Orhan)</li>\n<li><strong>Faster pages</strong>: dashboards load card by card and the heavy reads were rewritten, so pages open quickly on a full company's data (Orhan)</li>\n<li><strong>Honest charts</strong>: a chart no longer drops at its right end because the current period is not over, and axes use even steps (Orhan)</li>\n<li><strong>One sidebar, dark mode and the Argus look</strong>: the product was renamed from Cockpit to Argus, with a new logo, one left sidebar, a theme switch, plain wording and a layout that works on a phone (Orhan)</li>\n</ul>\n<h3>Data and connections</h3>\n<ul>\n<li><strong>Integrations</strong>: a page to connect each tool with a key, a sign-in or a ready-made preset, and to change a connected tool's settings later (Orhan)</li>\n<li><strong>New connections</strong>: Stripe, Paddle, Paddle Classic, Zendesk, Intercom, Xero, HubSpot, Mixpanel, Google Search Console, Google Analytics, Gmail, Linear, GitHub, AWS, Mailgun and AnnounceKit can be read (Orhan)</li>\n<li><strong>Add to Slack</strong>: Slack connects through one Argus app, and the install screen picks the channel agents post to (Orhan)</li>\n<li><strong>Sync on connect, then hourly</strong>: a tool syncs the moment it is connected and every hour after, and one failing or slow tool no longer stops the others (Orhan)</li>\n<li><strong>Knowledge</strong>: help center articles, website pages and company notes are collected into one searchable library that agents read (Orhan)</li>\n<li><strong>One data model and one set of metrics</strong>: every tool's records are stored in one shape, and each metric is computed one way for every company (Orhan)</li>\n<li><strong>A data warehouse as a source</strong>: a company can connect its warehouse, Snowflake first, and have revenue read from it (Orhan)</li>\n<li><strong>Monthly revenue corrected</strong>: a subscription moved between two billing systems counted twice, discounts were ignored, and past months used today's prices. All three are fixed for Paddle and Stripe (Orhan)</li>\n<li><strong>AnnounceKit's history brought over</strong>: the customers, billing and agent history of the old AnnounceKit admin were imported into Argus, with an import that resumes after a dropped connection (Orhan)</li>\n</ul>\n<h3>Access and security</h3>\n<ul>\n<li><strong>General managers run their own workspace</strong>: a workspace admin can hire agents, configure them, switch them to live and pause them without Balio's help (Orhan)</li>\n<li><strong>Invite your team and Preferences</strong>: a general manager invites their own people, and Settings has a Preferences tab (Orhan)</li>\n<li><strong>Personal mail and calendar stay personal</strong>: rows from a person's own mailbox and calendar are visible to that person only (Orhan)</li>\n<li><strong>Security review and fixes</strong>: four audits of security, company separation, code and readiness were written, and the first findings were fixed, among them connections that could be pointed at another address (Orhan)</li>\n<li><strong>Privacy policy and About pages</strong>: two public pages that Google requires before a company can connect its Google account (Orhan)</li>\n</ul>\n<h3>Balio's side</h3>\n<ul>\n<li><strong>Foundry desk</strong>: Balio's page for requests from workspaces. A request for a team of agents is answered with one action that installs it in draft (Orhan)</li>\n<li><strong>Modules</strong>: every dashboard and feature can be switched off for a workspace from Foundry (Orhan)</li>\n<li><strong>Onboarding and company profile</strong>: a setup wizard for a new workspace, a Settings page, and one company profile that agents and pages read (Orhan)</li>\n<li><strong>Demo company</strong>: a sample company named Ground Zero for showing the product, kept out of the portfolio numbers and never run by the scheduler (Orhan)</li>\n</ul>\n<h3>Platform and engineering</h3>\n<ul>\n<li><strong>The agent runner</strong>: the service that runs agents and syncs moved to Cloudflare, with separate lanes for support and scheduled work so a busy company does not hold up the rest (Orhan)</li>\n<li><strong>Staging and production releases</strong>: the dashboard is deployed as its own service, with a written guide for staging and production (Orhan)</li>\n<li><strong>Tests before every release</strong>: a release now waits for the full test run to pass, and database changes are checked for order and safety first (Orhan)</li>\n<li><strong>Read-only diagnose tool</strong>: a way to run a read-only question against production data, with ready reports on revenue, connections, agents and page speed (Orhan)</li>\n<li><strong>Simulated tools for testing</strong>: stand-ins for billing, support, chat and help center tools, so agents are tested end to end without touching a real account (Orhan)</li>\n</ul>",
            "url": "https://argus-changelog.announcekit.app/release-notes-5-to-11-oct-the-agents-floor-an-approval-inbox-jarvis-1AEIik",
            "title": "Release notes, 5 to 11 Oct: the Agents floor, an approval Inbox, Jarvis",
            "summary": "The first week of Argus: one workspace per company, where agents do the routine work, people approve what goes out, and the company's numbers sit on one set of dashboards.",
            "date_modified": "2026-10-11T16:00:00.000Z",
            "tags": [
                "announcement"
            ]
        }
    ]
}