Changelog
Every change to vishvakarma, newest first. Releases are git tags (all tags, GitHub releases); the source of this page is CHANGELOG.md.
v0.3.12026-11-02release ↗
- dsr: one fixed structure, a thread per week, links to the commits. The skill no longer studies past DSRs for their format: it's written down (greeting, date, the Time | Tasks table, the day's commits grouped by project, sign-off) and
dsr_render.pyproduces it. Weeks run Monday to Saturday: Monday's DSR is a new mail with the week's subject (subject_template), Tuesday to Saturday reply to everyone in that thread; Sunday is refused. Recipients aretoandccin dsr.toml (a name alone is looked up once, then saved with its address). dsr_commits.pygives each commit its GitHub or GitLab link and whether it's pushed;dsr_render.py --commitsputs the pushed, non-merge ones at the bottom and refuses unpushed ones (their links wouldn't open) unless--skip-unpushed. It also writessend.json: new or reply, the subject, the search for the week's thread, to and cc.
v0.3.02026-11-02release ↗
- Renamed from kaushal to vishvakarma (विश्वकर्मा, the divine craftsman). The command is
vishvakarma, the repository github.com/Theyashsawarkar/vishvakarma (the old address redirects), the servicevishvakarma.service. The first run moves your skills and settings (~/.config/kaushal) to~/.config/vishvakarma; Vayu's MCP servers it hands to agents carry their new names too (narada, vaikhari, dvarapala).
v0.2.22026-11-02release ↗
- Fixed the tests after darshan joined (v0.2.1 failed CI, nothing else changed).
v0.2.12026-11-02release ↗
- darshan joins the MCP servers: agents can show you a file and hear what you ask about it.
v0.2.02026-10-28release ↗
- The app,
kaushal ui: every skill, tool and agent in three tabs, in the look of Vayu's other terminal tools. Read, edit (Vayu's: your own copy) and create skills, edit their settings; test a tool (start it, do the MCP handshake, list its tools); see what every agent has and what a sync would change; sync, doctor, turn things off, take back one agent's, all without leaving it. Follows varna's theme. kaushal off NAME/kaushal on NAME: turn a skill or tool off for every agent and back (~/.config/kaushal/off.toml).- A launcher entry ("kaushal"), installed by install.sh.
- A Skills page on the website: every skill as a card, and a page for each with its full instructions and files, linked from every page's top bar. The README's skills list is now written from skills/, so it never misses one (
scripts/site.py, around the shared site generator).
- prasar joins the MCP servers: agents can check, draft and propose posts for X and LinkedIn; every post waits for the user's approval.
- A website: theyashsawarkar.github.io/kaushal, built from the README, this changelog and seven decision records (docs/adr/) by the generator every Vayu tool shares; a how-it-works diagram; the README explains how kaushal works in Vayu.
v0.1.02026-10-28release ↗
- Skills for every agent. Skills are folders with a SKILL.md (the open Agent Skills format): Vayu's ship in
skills/, yours go in~/.config/kaushal/skills/(kaushal new NAME).kaushal synclinks them into Claude Code (every vesha profile shares them), Codex and the shared~/.agents/skills, which opencode and other agents read; agents that don't read skill folders get an index in their instructions file. - Tools for every agent.
mcp.tomllists Vayu's MCP servers (anumati, ekatva, sandesh, sangam); sync registers the installed ones with Claude Code (every profile, vesha's included), Codex, Gemini CLI and opencode.{agent}in args or env becomes the agent's name. Yours go in~/.config/kaushal/mcp.toml;enabled = falseleaves one out. - Never touches what isn't its own: what it added is recorded, a skill or server removed from kaushal is removed from the agents, a folder or server of yours with the same name is left alone, and
kaushal unsynctakes everything back.kaushal doctorchecks it all. - Synced at login (
kaushal.service) and on install, so a new agent or account gets everything without asking. - The
dsrskill: the Daily Status Report, from the day's commits to an HTML table sent as a reply-all in the DSR thread, with scripts that collect the commits (dsr_commits.py) and check and render the timetable (dsr_render.py).