[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-93904":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":9,"totalLinesOfCode":9,"stars":12,"forks":13,"watchers":14,"openIssues":14,"contributorsCount":9,"subscribersCount":14,"size":14,"stars1d":14,"stars7d":14,"stars30d":14,"stars90d":14,"forks30d":14,"starsTrendScore":14,"compositeScore":15,"rankGlobal":9,"rankLanguage":9,"license":9,"archived":16,"fork":16,"defaultBranch":17,"hasWiki":16,"hasPages":16,"topics":9,"createdAt":9,"pushedAt":9,"updatedAt":18,"readmeContent":19,"aiSummary":20,"trendingCount":14,"starSnapshotCount":14,"syncStatus":21,"lastSyncTime":9,"discoverSource":22},93904,"aw-webui","ActivityWatch\u002Faw-webui","ActivityWatch","Webapp for visualizing and browsing ActivityWatch data, built with Vue.js.",null,"https:\u002F\u002Fgithub.com\u002FActivityWatch\u002Faw-webui","Vue",143,168,0,43.68,false,"main","2026-09-21 04:01:26","# aw-webui\n\nA web-based UI for ActivityWatch, built with Vue.js\n\n[![Build Status](https:\u002F\u002Fgithub.com\u002FActivityWatch\u002Faw-webui\u002Fworkflows\u002FBuild\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002FActivityWatch\u002Faw-webui\u002Factions)\n[![Coverage Status](https:\u002F\u002Fcodecov.io\u002Fgh\u002FActivityWatch\u002Faw-webui\u002Fbranch\u002Fmaster\u002Fgraph\u002Fbadge.svg)](https:\u002F\u002Fcodecov.io\u002Fgh\u002FActivityWatch\u002Faw-webui)\n[![Known Vulnerabilities](https:\u002F\u002Fsnyk.io\u002Ftest\u002Fgithub\u002FActivityWatch\u002Faw-webui\u002Fbadge.svg)](https:\u002F\u002Fsnyk.io\u002Ftest\u002Fgithub\u002FActivityWatch\u002Faw-webui)\n\n## Getting started\n\nGetting started with setting up the development environment is pretty straightforward:\n\n```bash\n# Start an instance of aw-server running in testing mode (on port 5666, with a separate database),\n# This is what the web UI will connect to by default when run in development mode.\naw-qt --testing\n# or, to run without watchers:\naw-server --testing\n\n# Install dependencies\nnpm install\n# or, to get exact versions of dependencies:\nnpm ci\n\n# start aw-webui in dev mode\nnpm run serve\n```\n\nAlternatively, you can run `make dev` to install dependencies and serve the application locally.\n\nYou might have to configure CORS for it to work, see the CORS section below.\n\nYou may also want to generate fake data so you have something to test with, see: https:\u002F\u002Fgithub.com\u002FActivityWatch\u002Faw-fakedata\u002F\n\n## Building\n\nTo build the production bundle, simply run the following:\n\n```bash\n# Install dependencies\nnpm ci\n\n# Build for production\nnpm run build\n```\n\n## Using a pre-release with your main install\n\n**Note:** Running a development version of aw-webui with an old aw-server can lead to issues due to version incompatibilities.\n\n### By copying the web-assets to your main install\n\nYou can run a development version of aw-webui with your main version of ActivityWatch by building it (or fetching the latest build from CI) and replacing the contents of the `static` directory of your aw-server (or aw-server-rust) installation. For simplicity, back up the original directory for easier switching back.\n\nThe assets are stored in the following directories (relative to your installation directory), depending on if you use aw-server-python (default) or aw-server-rust:\n\n - aw-server-python: `activitywatch\u002Faw-server\u002Faw_server\u002Fstatic\u002F`\n - aw-server-rust: `activitywatch\u002Faw-server-rust\u002Fstatic\u002F`\n\nYou can copy the assets manually from your `make build` or `npm run build` output to the above locations.\n\nOnce you've put the files in the directories, you may have to do a hard refresh in your browser to invalidate any stale caches.\n\n### Using `--webpath` with aw-server-rust\n\nInstead of copying files, `aw-server-rust` supports loading the web UI from a custom path via the `--webpath` flag. This is especially useful on platforms where the server bundles static assets into the executable (e.g. Windows):\n\n```bash\n# Point aw-server-rust to your local build output\naw-server-rust --webpath \u002Fpath\u002Fto\u002Faw-webui\u002Fdist\n```\n\nThis avoids having to copy files and makes it easy to switch between development and production builds.\n\n### Using your main install's data\n\nIf you want to actively iterate on `aw-webui` with your local production data (with your production server running), you'll want to use a development build, automatically update it, and connect to your production data. To do this, in `aw-webui` source directory, in one terminal window run:\n\n```bash\nAW_SERVER_URL=\"'http:\u002F\u002Flocalhost:5600'\" npx vue-cli-service build --watch --dest=..\u002Faw-server\u002Fstatic\n```\n\nIf you want to add `debugger` statements in your code and otherwise break linting rules, you'll need to add a `--skip-plugins=no-debugger` to that command.\nThen, in another terminal (with your venv activated) run:\n\n```shell\npython3 -m http.server --bind 127.0.0.1 27180 --directory ..\u002Faw-server\u002Fstatic\n```\n\n## Tests\n\nTests can be run with:\n\n```bash\nnpm test\n```\n\nThere are also E2E tests. You need to have an aw-server and the web UI running in development mode (with `npm run serve`, as instructed above). After you have that setup, you can run the tests with:\n\n```bash\nmake test-e2e\n```\n\n## Development\n\n### CORS\n\nFor development, you'll also have to add\u002Fchange CORS configuration in the `aw-server` configs by adding `cors_origins = http:\u002F\u002Flocalhost:27180` to your\nconfiguration file `\u002Factivitywatch\u002Faw-server\u002Faw-server.toml` under respective sections (`server-testing` section when running server in testing mode).\n\n### Code structure\n\nOne of the first things that happen in the application is the execution of `src\u002Fmain.js`. This loads things such as bootstrap-vue and a bunch of other stuff that's globally used (filters, resources).\n\nThe main.js file then loads the `src\u002FApp.vue` file, which is the root component of the application.\n","aw-webui 是一个基于 Vue.js 构建的 Web 前端应用，用于可视化和交互式浏览 ActivityWatch 采集的用户计算机活动数据（如应用使用时长、窗口焦点、键盘鼠标活动等）。它通过 HTTP API 与 ActivityWatch 后端（aw-server）通信，提供时间线视图、统计图表、会话过滤与自定义查询等功能，支持本地部署与开发集成。项目轻量、模块化，适合作为个人生产力分析、数字健康监测或行为习惯研究的数据展示层，常与 aw-server-python 或 aw-server-rust 搭配使用。",2,"trending"]