Changelog
What changed in Kodela, written for the people who run it. Release names are the ones the console footer shows; numbers are pull requests.
Kodela · orxy V1.7.2.2 · V1.7.3 · 4 Oct 2026
- V1.7.3 · FeatureThe console fits phones and tablets: pages no longer scroll sideways or squeeze into a narrow strip, and the menu opens as a drawer that works from the keyboard.
- V1.7.2.2 · FeatureThe organisation’s Audit tab is a dashboard: a timeline by day, refused counts that filter with one click, and records grouped by question, each written as a sentence.
- V1.7.2.2 · FeatureOpen a record to see how it happened (authorship, agent run, approver, model), copy a link to it, or show it exactly as stored.
- V1.7.2.2 · FeatureAn integrity panel says whether the audit log’s chain verifies and how many pushes carry a verified signature, or that the check did not report.
- V1.7.2.2 · FeatureExport exactly the current filter as CSV or JSON, safe to open in a spreadsheet; the export is itself recorded.
- V1.7.2.2 · FeaturePassword sign-ins at the portal and the console are audited, allowed and refused, without the password and without saying whether an unknown address is an account.
- V1.7.2.2 · SecurityAn organisation’s audit shows only records provably its own, and says how many it withheld and why.
- V1.7.2.2 · FixA plain member is no longer offered the Audit tab; it is for owners, admins and auditors.
8 changes · printed from the release history
Earlier releases and merges
Kodela · orxy V1.6 · V1.7 · V1.7.1 · 4 Oct 2026
- FeatureA new workspace gets its own Postgres database by default. “None” and “Connect my own server” are still choices.
- FeatureWhere a database can’t be added, such as on a member’s own computer, the workspace is created without one and says why.
- FeatureA read-only Database tab lists the workspace database’s tables and columns, or says why it can’t.
- FeatureAn AI usage tab for organisation admins and auditors: requests, tokens and cost by member, workspace, tool, provider, model and account.
- FeatureRequest a usage report and download it as a spreadsheet; every download is recorded.
- FeatureA Docker tab in the workspace: its containers, with logs, stop and restart, and the images it may use.
- FeatureA Compose project that brings its own Postgres uses the workspace database instead, and the Run box says so.
7 changes
Kodela · orxy V1.5.1 · V1.5.2 · 3 Oct 2026
- FeatureThe AI agents in the chat can run Docker commands in a workspace that has Docker switched on. A workspace setting, on by default once Docker is on, turns this off from the Docker card.
- FixDocker commands from the chat reach the workspace’s own Docker instead of being refused.
- FixAn approval request for a Docker command gives the right reason, not a file diff.
- FeatureA release history in the console, for platform operators only, with search and New / Fixed filters.
- FixThe preview of an app built with no base path, such as a production Next.js build, is no longer blank.
- FixA previewed app’s own /api calls and WebSocket connections reach the app, and a refresh reloads the app.
6 changes
Kodela · orxy V1.5 · 2 Oct 2026
- FeatureA member’s computer updates its own Kodela agent.
- FeatureThe Windows installer checks free disk space, sets up WSL and Rancher Desktop, and offers to install what is missing.
- FeatureChat, files, search, git and approved commands reach a workspace on a member’s computer.
- FeatureAI agent runs work on a member’s computer, while the organisation’s AI sign-in stays on the platform.
- FeatureThe Your computers page shows each workspace as a tile with its state and an Open button.
- FeatureMembers can ask their organisation for a repository or an AI model.
- SecurityOffboarding a member archives the workspaces on their own computer.
- FixA broken network on a member’s computer repairs itself instead of blocking every new workspace.
- FixA computer that is added again replaces its old connection.
- FixA connection on a member’s computer that cannot start says why, in the portal.
- FixA task interrupted by a restart is settled instead of showing as running for ever.
- FixRemoving a computer asks first and releases its workspaces.
12 changes
Kodela · orxy V1.4 · 1 Oct 2026
- FeatureDocker and Docker Compose in a workspace. Off by default: an organisation allows it, it is switched on per workspace in either create form, and a Docker card shows what is running.
- SecurityEach workspace’s Docker sees only its own containers and networks. Pulled images are a shared cache on the host. Docker is not available for a workspace on a member’s own computer.
- FeatureApps started with Docker Compose open on the workspace’s own address, and the Run box can start them.
- FeatureThe chat knows whether the workspace has Docker and what is running.
- FeatureThe chat knows the structure of the workspace database, and the Library can connect a project to it.
- SecurityStarting and stopping Docker apps is written to the audit log.
- FixFull Docker reads as unavailable on a host that cannot run it safely, instead of failing later.
- FixAn image pulled by its exact digest is recorded and matched correctly.
- FixLong chat answers no longer show “Connection dropped” and reload the conversation.
- FixA failed database read keeps the last known structure instead of losing it.
- FixThe chat’s full-width button no longer sits over Delete.
11 changes
Kodela · orxy V1.2 · V1.3 · 30 Sep 2026
- FeatureA Mac can host workspaces: the Kodela agent runs in a container beside them.
- FeatureThe product is named Kodela everywhere a person reads it, including what workspaces and their AI agents read.
- FeatureAdmin, organisation, workspace and portal screens show one plain line, with the rest behind Learn more, in a more modern look with the same colour theme.
- FixAfter a restart of a member’s computer, Claude, Codex, the portal and git keep working.
- FixCreating a workspace stops when a storage folder is refused, instead of carrying on.
5 changes
Kodela · orxy V1.0 · V1.1 · 29 Sep 2026
- SecurityA secret typed into the chat is refused instead of being sent.
- SecurityA member’s own AI key is theirs alone. Organisation admins can see which members hold one, never the key itself.
- SecurityAn organisation can mask personal data in what its chat sends.
- Securityssh, rsync and ftp are refused on any port when File transfer is off.
- FeatureAttach images, PDFs and text files in the workspace chat. #247
- FeatureA workspace can be created with a Postgres database. #248
- FeatureA member’s own laptop can host their workspaces, with image sync of only the missing layers, preview, time-limited access, and offboarding that disables their computers. (#249, #250)
- FeatureChoose Node, Go, Rust, Java, .NET or Deno versions when creating or editing a workspace. #251
- FeatureA console refresh: new colours and fonts, rounded cards and pill buttons. #251
- FeatureStop sits in the chat box while a run is live, and stops AI agent runs too.
- FeatureEvery console form field has a label a screen reader announces.
- FixA write waiting for approval is no longer reported as completed.
- FixA refused Claude sign-in upload no longer removes the organisation’s other Claude sign-in.
- FixFour defects in the chat’s skill picker are fixed.
- FixA chat with no skills found no longer crashes.
- FixThe chat box no longer pushes Send off the screen.
- FixCopy buttons say so when they cannot work over plain http.
- FixApproving or discarding a run refreshes the Git pane at once.
18 changes
Kodela · main · 28 Sep 2026
- FixA chat turn shows its outcome on its status line, with Continue for a paused turn. #242
1 change
Kodela · main · 27 Sep 2026
- FeatureChoose skills for a chat conversation, from the Skills button or by typing a slash. #235
- FeatureAn organisation chooses which catalogue skills its members get. #230
- FeatureThe assistant pack: 24 personal-assistant catalogue skills, off by default. #232
- FeatureA UI review skill, with its checker, for apps built in a workspace. #239
- FixA catalogue skill copied into a workspace reaches Claude Code too. #234
- FixThe chat’s add menu opens above the panel. #240
6 changes
Kodela · hammy V1.01 – V1.1 · 26 Sep 2026
- FeatureA workspace can list, start and stop its owner’s workspaces over the workspace-to-console channel. Off by default. #225
- FeatureWorkspace requests, and an inbox where an app built in a workspace collects its users’ reports. #226
- FeatureAgent skills, and the same workspace standards for every agent. #216
- FeatureOffline quality and security tools in the workspace image, with scan, library and diagnostics skills. (#218, #219)
- FeatureDeveloper, research and media skills. #220
- FixPreview: a dev server can keep its path prefix, so hot reload works behind the preview route. #224
- FeatureThe workspace chat is redesigned: run results sit in each turn’s row, approvals appear inline, and the message box has a mode row.
- FeatureThe console scales up on larger screens, and the chat opens at a third of the width.
- FixA dropped connection no longer blanks the last chat turn; the turn is kept and followed.
- FixWorkspace files no longer become owned by root, so a later create records the owner.
- FixThe repository catalogue has one Add button, plus Add discovered.
11 changes
Kodela · lychee1.0 – lychee1.5 · hammy V1.00 · 25 Sep 2026
- SecurityThe developer portal lists only your own workspaces.
- FeatureA chat permission can last until it is revoked, and that is now the default.
- FeatureThe Library’s selected project can switch branches.
- FeatureAttach images in the workspace chat for Claude to read.
- FeatureA console redesign: one font family and size scale, a decluttered portal and a tidier admin console, with no change to what it does.
- FeatureThe release name shows in the developer and admin footers.
- FixInvitations can be deleted, not only revoked.
- FixThe application asks its own questions instead of browser pop-ups.
- FixThe organisation page’s Refresh works, and a new repository reaches the Workspaces tab.
- FixLeaving a workspace returns to all workspaces instead of signing you out.
- FixThe signed-out portal page is no longer blank.
11 changes
Kodela · main · 24 Sep 2026
- SecurityWorkspace DNS resolves only through each organisation’s allowlist filter. #207
- SecurityThe File transfer setting now governs the IDE, copy tools and direct GitHub from a workspace. #205
- SecurityThe browser IDE obeys the File transfer setting. #202
- Securityscp, sftp and rsync over Desktop IDE attach obey File transfer too. #204
- FeatureA workspace container removed without a destroy record is written to the audit log. #214
- FixBrokers listen on each organisation’s gateway, so its workspaces can reach them. #215
- FixA broker restart no longer strands git in running workspaces. #197
- FixThe live store is kept out of the image build context. #213
- FixCluster views restored, and the file-copy egress check narrowed. #210
- FixTest fixture only: the tenant-isolation suite’s fixture had drifted, which caused its three failures. No product change. #209
10 changes
Kodela · main · 23 Sep 2026
- SecurityAn organisation network with no egress rules is named instead of passing silently. #191
- FeatureThe Connect pane: a desktop attach token shown once and never stored in the browser. A git broker refusal now shows its remedy. #188
- SecurityOnly the front door can reach a workspace’s attach bridge. #174
- FixThe browser IDE connects reliably; connections from foreign origins are refused before they are dialled. #195
- FixDesktop-attached ssh sessions get the workspace environment, so Claude works there. #193
- SecurityThe Desktop IDE attach switch warns that code can leave the platform. #194
- SecurityA check the default branch runs cannot be deleted in the same push to get past the validation gate. #185
- FeatureThe authorship record supports SHA-256 repositories. #184
8 changes
Kodela · main · 22 Sep 2026
- FeatureDesktop IDE attach: VS Code Remote-SSH, JetBrains Gateway and ssh, through a token-checked front-door route. Off by default. #162
- SecurityA front door that cannot check an attach token refuses instead of guessing. #169
- FeatureA Pull requests pane that reads GitHub through the broker. #155
- FeatureEvery push through the broker names who, or what, made its commits, in a record signed with a key held on the host. #149
- FeatureValidate this commit: the verdict the broker checks before a push. Off by default. (#135, #137)
- FeatureCurated, pinned VS Code extensions, with Claude Code in the editor on the brokered key. #141
- Featureopen-pr opens a pull request from the workspace terminal, through the broker. #144
- FixA chat reply cannot claim an approval card it never drew. #159
8 changes
Kodela · main · 21 Sep 2026
- SecurityThe broker refuses a push without a passing verdict for its exact commit, when the validation gate is on. #132
- FixSigning in over plain http to a host that declares TLS says why it cannot work. #131
- FixStopping a run that worked reads as an outcome, not an error. #133
- FeatureAn organisation admin can delete an account; a departed person’s workspaces are archived, not orphaned.
- FeatureRevoke a member, then re-invite them or delete and wipe their data.
- FixA parked write outside the project reads as asked for, not written, and names its path.
- FixA server with no mail relay says so on the password-reset screen.
- FixCopying an invitation link works over plain http.
8 changes
Kodela · main · 20 Sep 2026
- FeatureA project boundary: the agent works in its repository; anything outside is scratch, asked for, or refused.
1 change
Kodela · main · 19 Sep 2026
- FixA chat message counts as someone using the workspace, so the idle sweep leaves it alone.
1 change
Kodela · main · 18 Sep 2026
- FeatureThe chat as one stream with one picker, behind the new chat view toggle. #130
- Featurebin/provision-host brings the serving tier up on another machine over ssh.
- FixA failed start explains why, taken from the agent’s own output. #127
3 changes
Kodela · main · 17 Sep 2026
- FeatureEvery run and every chat turn records what it spent, in the same fields. #102
- FeatureEvery permission decision, and its reason, is recorded on the run. #112
- FixApproval answers reach the agent in the shape it expects, so an approval is an approval. #113
3 changes
From the release and merge history. Each entry restates a change in plain words. Deploy records, build and test process, planning notes and test-only work are left out, except where a title could be misread: #209 is listed so that no one takes it for a product change.
What this log does not tell you
- Released is not the same as running. An entry says what reached the main branch, not what any host runs.
bin/whats-runningsays that for yours. - Merged is not the same as proven. The validation gate and the authorship record are merged and deployed, and neither has yet been seen on a real GitHub push.
- Release names are build labels. The name in the console footer moves on with each build. It is not a semantic version or a support promise, and changes before 25 Sep are dated, not named.
- Docker in a workspace has limits. It is off until an organisation allows it. Pulled images are a shared cache on the host, so a workspace can tell that an image was already pulled. Full Docker needs a platform administrator and a supported runtime, and is not yet available on a standard install.
- The audit shows only what is provably yours. An organisation’s Audit tab withholds records that merely carry its name, and says how many. Its window is up to 90 days, never past your retention.
- Sign-ins are recorded from orxy V1.7.2.2 on. Password and shared-credential sign-ins are new in this release; single sign-on sign-ins are recorded as “signed in with SSO”. Earlier sign-ins are not in the trail.
- AI usage counts what it can see. Cost is recorded only where your organisation has turned cost tracking on; what isn’t measured shows as “not recorded”, never estimated. AI tools that hold their own login inside a workspace aren’t measured, and there is no spend cap.
- The Compose database swap is narrow. Postgres images only; apps that read their own database-host settings need changing, and a
docker compose uptyped by hand in the terminal is not redirected. - A member’s own computer is not the platform host. Docker is not available for a workspace there, and the organisation’s AI sign-in stays on the platform. Only the Windows installer has been tested end to end on real hardware; Linux laptops and Macs have not been yet.