Everything we have changed in Yomcom, newest first. Open a release to read what went out that day.
Money that comes back on its own, and a few things that only looked broken.
A workspace setup that fails now refunds itself. Setting a workspace up with AI charges before it
starts, and until now a run that died part way through — the service restarting under a retry, most often —
took the money with it and told nobody. What it charges is written down before anything can go wrong, each
part records what it gave back, and anything still owed by a run that never finished is returned
automatically. Every "Setup using AI" request is also kept now, with the three answers exactly as they were
typed, so support can see what was actually asked for.
And it can finish again. Two settings on the AI service were quietly stopping it: the reply size limit
was half what a workspace page needs, so pages came back cut in half, and the time limit was a minute
against a job that takes several, so every attempt was cut off and reported as the provider being busy. No
workspace page had been written for two days. Setup also asked to search the web on every run, which is only
useful when you paste a website address — and asking for it was enough to make the whole request fail, so
the description and the colours were being lost every time.
A generated workspace page fills the space it is given rather than stopping half way down with the
background showing beneath it.
Replying on a support ticket works from the ticket list. The reply arrow under a message did nothing
unless you had opened the ticket on its own page — which almost nobody does. Pressing it now opens a box
under the message you pressed, wherever you opened the ticket from.
The help assistant stops repeating itself. Asking it to change one of your modules could leave it
quoting the same price over and over and never taking the payment, however many times you agreed. It now
recognises what you already agreed to, and charges for and builds the words you were quoted rather than its
own rewording of them. Telling it that it is going wrong is now treated as a report to pass on, not as a
fresh instruction.
Smaller things: the "Show on our public page" row has gone from the ⋮ menu on module cards — your
workspace page's own Make public / Make private switch is where that lives; the credits and Yomcoin figures
in the side menu sit together properly on a phone; and the menu's four bottom buttons follow the side the
menu is on.
Behind the scenes: purchase invoices — what the business pays for — now have somewhere to live, with
VAT recorded from the start, so the accountant export can stop being an estimate.
On /platform/users, user cards currently waste a lot of horizontal space. Switch to a responsive grid layout with 1, 2 or 3 columns depending on scre
Workspaces you can make your own, and a site that looks after itself.
Any workspace can now have its own front page, not just public ones. Describe what you want and the
page is written for you — colours, header, background and all — and it applies only inside that workspace,
so making the family's page green does not repaint anyone else's. The generated page can draw a module's
⋮ menu, but it cannot act on it: the page asks and the platform does the work, so a design can never reach
anything it should not. Pages are moderated as they are generated, and while one is being written every
control it will change is disabled, so a refresh mid-generation no longer looks like nothing is happening.
Support tickets have a console. Super-users can read, reply to and resolve what comes in, and a reply
asks whose name it goes out under before it is sent rather than assuming.
Smaller things: every module now carries its own mark in the side menu; installing from the ⋮ menu on
Discover works again; uninstalling from the marketplace no longer 500s; and editing a description in
Documents replaces the text in place instead of downloading a file.
Behind the scenes — no visible change, but the reason the site should stay up. There is now a
standalone monitor watching every live service and page from a machine that is not the site, over two
different internet connections, so "the site is down" can be told apart from "the broadband is down". It
restarts what it can, checks the restart actually worked, and only writes to a human when it could not fix
the thing itself. Backups moved to a weekly base backup with continuous archiving, and the restore was
rehearsed rather than assumed — which found two faults that would have made those backups useless.
Audio generation now runs on our own hardware; two external providers were removed entirely.
The release modules got a price, and school got easier to sit.
Every module is now paid for in one of four ways, and it says which before you install it. Credits as
the module uses AI, bought once, a monthly subscription, or free with donations welcome. The first is not a
choice — a module already spending your credits on AI is already charging you, and selling it on top would
bill you twice for the same thing — so only a module that uses no AI is asked. Whatever the answer, the
price is on the card next to Install and you are asked to confirm the number before anything is taken. A
refusal now says what it costs, what is left and that nothing was charged, on the screen you are on.
Buying once means once: remove a module and put it back and it costs you nothing the second time. A
subscription renews when somebody opens the module rather than on a schedule, so a month nobody used it is
a month nobody paid for, and if a payment cannot be taken the module stops for that workspace and says so
plainly instead of vanishing. Nothing you already had starts charging you — every existing install was
grandfathered with a receipt.
Owners set their own price. It can be cut whenever and by as much as you like; it can be raised by at most
a quarter, and no more often than every ninety days, with the limits stated on the form before you hit
them. A price of zero is refused for the two models that carry one, and points you at donations instead.
The Terms now say what buying a module actually gets you: a licence to run it, not ownership.
Classroom fits the learner rather than the year group. Where a territory sits its qualifications at
more than one level — GCSE Foundation and Higher, and their equivalents — a learner is entered at one, and
everything they are taught is pitched there instead of at the top of their age group. The routes *below*
the compulsory qualification are offered too, which they never were. An adult picks which subjects their
learner actually studies, and can shape how a lesson is written: how many questions, plain language,
worked examples first, mostly multiple choice, and a note in their own words about what this learner needs.
Lessons also follow on from each other now. Each subject has a scheme of work in teaching order, and a
learner moves through it — so the next maths class picks up where the last one left off instead of being
drawn fresh each morning.
Smaller things. The Credits and Yomcoins pages are illustrated again, redrawn in a modern style rather
than the wartime-poster look they had. Saving your credit-usage arrangement saves it, instead of handing
you a JSON file. The Modules list on the platform console paginates, the dashboard header can search its
cards, and Tower Defense was rebuilt as a single drawn interface.
The release the 3D assistants arrived in, and a rearrangement of where your money lives.
Your workspace can have an assistant, and it is built rather than picked. Describe the one you want and
it is modelled, rigged and animated for you, then it lives on your workspace page — it can be grabbed,
thrown, and dropped, and it lands like something with joints rather than a falling brick. Elbows bend one
way, knees the other, and letting go of an arm no longer sends the whole robot spinning. An assistant is a
folder you can drop somewhere, so one can be published, shared and installed rather than rebuilt from
scratch by everybody who wants it.
Building one costs real money at a supplier, so the whole path was made to hold its nerve: a build that
fails partway is picked up where it stopped rather than started again, a supplier that is briefly
unreachable is waited for instead of counted as a failure, and a request the supplier itself refuses is
held rather than charged for. What a build was quoted is now recorded against what it actually cost.
The money screen became two money screens. What you spend and what you are owed were on one page and
were easy to read as each other. Now "Credits" is what you have and what it goes on, and "Yomcoin (cash)"
is what you have earned — with your yomcoins sitting beside your credits in the menu either way. The list
of what you have already spent moved behind its own button rather than being the longest thing on the page,
and your workspace's figures sit behind a Statistics chip on your settings instead of at the bottom of a
card about an address.
Plans stopped capping and started discounting. Every plan builds as many modules as you like; what a
bigger one buys is a better discount on everything you spend. There is a starter package you can buy
exactly once. Free credits arrive daily, are always spent before the ones you paid for, and cost the people
who supply modules nothing — nobody earns from them and nobody is charged for them.
Settings stopped being a filing cabinet. It was drawers inside drawers; it is one flow now, in the
order you would actually work through an account, with a chip menu across the top to jump to any part of
it. How your workspace signs in lives with the people it signs in, and closing a workspace lives with the
owner whose decision it is.
Signing up says who you are, and is harder for a robot. New accounts give a name, a territory and a
date of birth before they can use the place; existing accounts are untouched. Behind that, the checks that
tell a person from a script were tightened and put behind a single switch — with no CAPTCHA, and nothing
sent to anybody else. You can also report a problem without your name on it, and the form says plainly that
support can still see who you are, because they have to be able to answer you.
Modules can now leave. Every module has its own repository, builds on its own, and no longer needs the
platform's source to exist — which is the groundwork for other people supplying them. Along the way a
module's own settings got one home, a module that throws no longer takes a page down with it, and modules
that are asleep cost nothing until somebody opens one.
And a lot of small things. The accent colour is green. A folder is made by dropping one module onto
another rather than by naming an empty box first. A module's cover picture can be regenerated on demand.
Sharing a module opens a proper dialog. Text that was unreadable on the accent colour was fixed in 22
places. The sign-in flow recovers rather than bouncing you when a stale sign-on comes back.
A long list of things you asked for, and two of them change how money works.
Free credits are now a thing, and you can see them. Sign in on any day and a handful of free credits
land in your account — you will see them arrive. The menu shows what you have as two numbers, what you
bought and what was given, because they behave differently: the free ones are always spent first, so the
credits you paid for are never quietly used up while free ones are sitting there. Nobody who supplies a
module earns anything from free credits — and, just as importantly, nobody is charged for the AI they buy
either. Neither side gains or loses on work the platform gave away.
Plans no longer cap how many modules you can build. Every plan is unlimited now. What a bigger plan
buys you instead is a discount on everything you spend — 5%, 12% or 20% as you go up. And there is a new
one-off starter package: a small payment for enough credits to get your first module built, plus a
permanent discount, buyable once.
Yomcoins sit beside your credits at the bottom of the menu, so what you are owed is as visible as what
you can spend.
Your workspace helps you set it up. A brand-new workspace opens its own settings so you can name it
and give it a face; once that is done, it offers to design your first module until there is one. Folders
are made by dropping one module onto another rather than by creating an empty folder first, and there are
drop targets between the cards so you can still put a module exactly where you want it. "How your people
sign in" now sits with the People it applies to.
Your settings screen has been rebuilt. It was a page of drawers inside drawers; it is now a single
flow with everything visible, in the order you would actually work through an account, with a chip menu
across the top to jump to any part of it. Moving a workspace into another one lives here now, next to the
other things only you can do.
Everyone tells us who they are. New accounts fill in a short details page — a name, a territory and a
date of birth — before they can use the platform. Existing accounts are unaffected.
You can report a problem without your name on it. Tick the box and other people see "Anonymous". Our
support team still sees who reported it, because they have to be able to answer you — and the form says
so plainly rather than promising more than we can keep.
Financials reads better. The explanation of how you make money here is a popup that shows once instead
of a paragraph you scroll past every visit, and the longer explanations now sit behind (i) buttons on the
sections they belong to.
Signing up is harder for a bot and no harder for you. Better rate limiting, timing checks and traps
that automated sign-ups fall into, with no CAPTCHA and nothing sent to a third party.
Terms. We have said plainly that credits are not money: they pay for use of the platform, they cannot
be cashed in or transferred, and they have no monetary value outside Yomcom. The free credits above are
covered there too.
The big one this time is not a feature. We had an independent, route-by-route security review of the
whole platform — every page, every button, the marketplace, the module sandbox and the background
services — and we fixed everything it found before this release went out.
What that means for you. Nothing you need to do, and nothing was misused: this platform is still
small and every account on it is known to us. But several of the things found would have mattered a great
deal later, when strangers can supply modules and the marketplace is open. We would rather fix them while
the answer is "nobody could have", than after.
Fixed: credits could be taken for work that never happened. If anything went wrong in the moment
between paying for a module build and the build being queued, the credits were gone and the request was
not. Payment and the work it buys now succeed or fail together. Alongside that: builds that fail for good
are refunded automatically, requests nobody decides are closed and refunded after a week, and refunds for
requests raised here now actually reach the account that paid — previously that last one quietly did
nothing at all.
Fixed: a form could fail and say nothing. If a save failed, the page simply did not move — no error,
no explanation, and on the workspace settings popup that meant renaming your workspace looked like it had
not worked when it had. Failures are now reported on screen, everywhere, on every form.
Fixed: saving workspace settings could fail outright for any workspace after the first, because of a
clash in how directory connections were stored. Saving no longer writes a directory connection it was
never asked to make, and no longer floods your workspace history with entries about a setting you did not
touch.
Faster. The busiest thing in the database was a settings table being re-read dozens of times a page;
it is now read once. Two screens that queried once per item on screen now ask a single question. Pages
across the platform do noticeably less work to draw.
Better on a phone. Every screen has been measured at phone size: no sideways scrolling, every control
big enough to press, dialogs that fit and can be closed, sticky bars that sit where they should, and the
navigation drawer's own contents finally sized for a thumb.
On /admin/company, in the Organisation card's logo section: remove the separate "Upload logo" button. As soon as the user picks a fi
In the notifications popup (opened from the bell icon at the bottom of the menu, next to sign-out), only list UNREAD notifications.
On the Assistant admin page (/admin/assistant): replace the "Generate new" button's text label with a "
When the user opens the assistant/chatbot panel, focus should be placed automatically in the chat message textbox so they can start typing immediately without
Requested by Christian (super-user) on /admin/apps.
Below the "Installed Modules" expander card, ad
On /platform/dev-tasks, the task textboxes refresh periodically and reset scroll position, jumping the user back to the top while reading/ — reviewed, not a bug
On /platform/settings, cards should be retracted/collapsed when a user first arrives at the page, rather than expanded.
User feedback: this screen's layout needs improving. From screenshot: fields feel cramped/inconsistently spaced between cur
On /platform/releases: each release card should be wrapped in an expander (collapsed by default, can be expanded to show full detai
On the dev tasks/AI developer screen, the task text field refreshes on every render, causing the scroll position to jump back
Users should be able to upload and attach files to their chat messages via a dedicated button positioned below the send button.
The chatbot input text box needs to:
Remove the 'Marketplace', 'Contact Us', and 'About Us' links from the header navigation on the public landing page (
Each task on the dev-tasks screen needs a dedicated 'Submit' button that disables the input textbox and allows the AI modera
On the AI developer screen, completed/implemented items should be hidden in a collapsed expander to keep the active task queue clean
On /platform/dev-queue, when the user clicks 'Apply Now', the console should start refreshing and displaying output in real-time. Currently
On the /platform/dev-tasks page, when a user clicks the approve button on a task, the task status should update immediately in th
Add a 'raised by' field to dev tasks so developers can submit multiple tasks at once and then approve/review them in batch from the dev-tasks list. Each task should s
When the AI developer finishes building a task, it should automatically remove that task from the dev board instead of leaving it there marked as d — reviewed, not a bug
Account menu: change the menu item label from 'Security' to 'Settings'. The Security page remains the same; only the label in the navigation menu changes.
?ref=…) whose referrer isn't a registered account no longer blocks sign-up. Previously such a link stopped the account being created at all — no verification email, and every retry failed the same way. Now the account is created normally and the unrecognised referral is simply dropped; a mistyped referrer entered by hand still shows a clear error so genuine typos are caught.