Repository navigation
An agent in the design: skills, instructions, the project folder and its history, and a sample document that teaches the basics.
Download
| System | File |
|---|---|
| macOS, Apple Silicon | Kalka-0.2.0-beta.1-arm64.dmg |
| macOS, Intel | Kalka-0.2.0-beta.1.dmg |
| Windows | Kalka-Setup-0.2.0-beta.1.exe |
| Linux | Kalka-0.2.0-beta.1.AppImage |
Kalka updates itself from 0.1 beta 6 on Windows and Linux. On macOS, download the new DMG and replace the app. Builds are not signed with an Apple certificate yet: if macOS blocks the first launch, open System Settings › Privacy & Security and click Open Anyway.
Added
- Agents can be given skills, rules and documents. Kalka comes with seven design skills, asked for in the conversation with a slash:
/direction,/landing-page,/copy,/critique,/responsive,/polishand/anti-slop. You can turn any of them off and add skills of your own, kept in the app and offered in every document. A Kalka folder keeps, in aninstructionsfolder it starts with, a summary and rules read with every conversation, its own skills, which add to the others or replace one by name, and documents cited with an at sign (@brief.md). Typing/or@in the conversation lists them, a line under your request says how many instructions went with it, and the Instructions panel, under the agent in the rail, shows them all. Markdown files open as they read, with their text one press away to write them; in the desktop app the project's files are written there. - The Folder panel lists a document's files as a tree, each kind with its own icon and color, and opens one in place of the canvas when clicked: code with line numbers, or the picture. A page opens on its clean HTML, as exported, with the file as saved one press away. While a file is open, the top bar shows its path and the way back in place of the screens, zoom, and preview. In the desktop app it is the folder the document is saved in, with what Git says changed; in a browser, or for a document not saved as a folder, it is the folder Kalka would write. In the desktop app, Save As Folder… there writes that folder to the computer, which is how an imported
.figbecomes a Kalka folder. - In the desktop app, the History panel keeps a folder's versions in Git, as a timeline, and publishes them online: paste the address of an empty GitHub repository (or any
https://orgit@Git address) to connect it, then each recorded version is published too. When Git has no name and e-mail to sign versions with, the panel asks for them and keeps them in the folder. Signing in uses the Git already set up on the computer, and a history Kalka starts ignores.DS_StoreandThumbs.db.
Changed
- The sample document, opened from the home screen and on demo.kalka.design, is now Learn the basics: one page of six lessons drawn on real layers, from selecting and moving to the agent and the folder, with the shortcuts to keep. Kalka's landing page is no longer the sample.
- The editor has a new shell. A top bar holds the logo, which opens the File, Edit, View, Object, Text, and Arrange menus outside the macOS desktop app, the document's name with undo and redo, the screens of the page in the middle with a plus to add a tablet or phone breakpoint, then the agent, zoom, preview, and sharing. An icon rail at the left edge switches the left panel between the agent, Instructions, Layers, Assets, Code, Folder, History, and the design check with its problem count; the right panel is Design alone. The highlight glides to the entry chosen in the rail and its lists, as in the page list.
- The editor is neutral: no colored light behind the canvas, opaque panels, and greys without a blue tint in both themes, so the app's own colors never tint the design. Its icons come from Hugeicons instead of Lucide.
- The agent's conversation opens in the left panel, from the rail, the sparkle in the top bar, or a field at the end of the toolbar. It reads calmer: the agent's replies sit on the panel as plain text, and a run of tool calls is one line, with Kalka's loader and what the agent is doing while it works, then the number of actions; the calls open on a click.
- Connecting an AI takes one choice instead of four steps: pick an agent already on this computer (Claude Code, Codex, Gemini CLI, Pi) and it connects, or pick a provider, paste its key, test it, and start. The same choice is in the agent's panel, in Settings › AI, on Home, and after the welcome; guided setup stays in Settings for several models and roles.
- Cursors on the canvas are a plain arrow with a filled name tag. An agent's has a sparkle before its name, and is orange when you work alone, so it never reads as yours.
- A layer whose name differs from its HTML shows its first class, or its tag, beside its name in the layers panel.
- Design check markers are off on the canvas until you turn them on from View › Design Issues.
- Home opens on the Kalka mark, the greeting, and the request to the agent centered on the brand backdrop, with joining a room, opening a file, and a new blank design under it; settings are a button in its corner.
- The welcome is one screen instead of three steps: your name, with Kalka drawn as a selected layer, and one button that connects the agent already on your computer, with driving Kalka over MCP beside it and skipping in the corner. Theme and code format stay in Settings.
- The editor tour goes through what is new for someone coming from another design tool: layers as elements, live code, screens, the agent, the folder and its history.
Fixed
- Following an agent survives a click on the canvas and zooming, so you can select and edit beside it; scrolling the view away still stops following.
- On a demo site such as demo.kalka.design, the root opens the demo document and no welcome, AI setup, or recovery dialog appears, including on later visits answered from the browser's cache. The demo opens on the first screen of Kalka's landing page instead of the whole page at 11%.
- The two center pins of the constraints diagram cross in the middle of the box instead of sitting side by side.
The full list is in CHANGELOG.md.