GRUENCY / Software / WS.AgenticOS
WS.AgenticOS: how GRUENCY keeps its AI work in view.
A local panel over Claude Code. It maps every memory file, skill and routine, shows what each skill and routine costs in tokens, and lists what to fix next.
Runs on our own computerScanner only readsPlain-text memoryNo external libraries
What the panel shows
Claude Code does the work. WS.AgenticOS shows what it works with: what it knows, what it can do, when it runs on its own and what that costs.
Memory
Plain-text notes, filed by department. The map shows every file, its links and its age, so stale or orphaned notes stand out.
Skills
Written procedures Claude follows for recurring jobs. The panel counts how often each one runs and how many tokens it uses.
Routines
Scheduled jobs that run without anyone asking. The panel lists each one with its schedule, its weekly cost and a weekly limit.
Usage and next steps
Tokens per day, project, skill and sub-agent. Suggested fixes go into a basket that becomes one instruction for Claude.
What the company knows, on one map
Every memory file is a dot, newer files on the inner rings. Colour marks the area: warm for WS.COMPUTER, cool for GRUENCY. Lines join files that refer to each other, and skills and routines sit outside.
- WS.COMPUTERClients and builds 60Configurator and prices 45Website and SEO 35
- GRUENCYApplications 50gruency.com 40
- SystemInfrastructure 30Memory 40
- Other 20
- Skills 48Routines 9
The start screen
It answers three questions: what ran, what it cost, and what needs attention. Ticked suggestions become one instruction for Claude, which a person reads before it runs.
Routines, next 24 hours
- Price check, WS.COMPUTER06:00done
- Site health, GRUENCY07:30done
- Notification digest12:00done
- Memory review17:00next
This week: 3.1 M of a 6 M token limit
Tokens by department, 7 days
Next steps
- 12 memory files not opened in 90 days: merge or retirememory
- 2 skills do mechanical work on the largest model: move to a smaller onecost
- 1 routine reports even when nothing changed: report only on findingsroutine
2 in basketCopy instruction for Claude
How it is built
- Memory, skills, routines, session logsPlain files on our own computer
- ScannerReads them and changes nothing
- PanelAnswers only on this computer
- A personPicks what to change
- Claude CodeMakes the change, as in any session
- Local only
- The panel adds no online service. Claude Code itself still talks to Anthropic, as it always does.
- Read-only scan
- The scanner never edits a file. Every change goes through Claude, with a person approving it.
- Plain text
- Memory is ordinary text files with an index. No vector database: a person can open, read and correct every note.
- In development
- Starting skills from the panel in the background, and a calendar of routines. Neither is in use yet.
One system for three kinds of work
Workstations
WS.COMPUTER builds: component prices, product cards, BIOS guides and service reports follow written skills, so each build is documented the same way.
Software
GRUENCY applications and this website: design rules, copy rules and release steps live as skills, and a critic agent scores pages before release.
Research and data
Measurement series, tables and papers: skills hold the method, and the memory keeps what was decided and why.
A system like this for your team
Sebastian Michalski built WS.AgenticOS for GRUENCY in October 2026. Under technical advisory, he can plan a similar set-up with your team: memory, skills, routines and cost limits around your own work.
