obsidian-time-ruler

A drag-and-drop time ruler combining the best of a task list and a calendar view (integrates with Tasks, Full Calendar, and Dataview).

Could not verifysource: GitHubTypeScriptMITcommit afbede327bc5

TypeScript, MIT licensed. The project labels itself: calendar, obsidian, task manager and time blocking.

Argusic could not get obsidian-time-ruler running. An Argusic agent installed it in 3 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Dependencies installed, TypeScript type-checks pass, esbuild production build generates valid plugin output (main.js + styles.css + manifest.json), and the OAuth server component starts and serves HTTP on port 3000.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 80 of 100 (the mean of this project's run scores).

At a glance

verdict
Could not verify
Argusic Score
80 / 100
cost of the verifying run
$0.02 (measured)
recorded runs
2
last tested
stars
352
forks
14
open issues
17
watchers
6
size
10 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing obsidian-time-ruler, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • tsconfig.json references vite/client types not present in dependencies1 minute
  • TypeScript error: Type 'Timeout' not assignable to type 'number' in autoScroll.ts1 minute
  • Build script with VAULT env tries to mkdir //.obsidian/plugins (EACCES)1 minute
Install time
3 minutes
Cold machine to finish
5 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
pnpm run build:dist exited 0 producing dist/main.js (3MB) and dist/styles.css (22KB); tsc -noEmit -skipLibCheck exited 0; server/ main.ts started on port 3000, responded to GET / with 404 and to GET /auth/google with Google OAuth redirect
Model tokens used
136,827
Exact commit tested
afbede327bc5
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Whether it works at all
this run verified nothing, so this page makes no claim either way

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

- verified_how: "pnpm run build:dist exited 0, dist/main.js (3MB) and dist/styles.css generated; se…
- final_state: Clean install, dependencies resolved, TypeScript type-checks pass, esbuild productio…
**Issues & Fixes:**
1. **`tsconfig.json` referenced `"types": ["vite/client"]`** — `vite` not in dependencies → changed…
2. **`src/services/autoScroll.ts`** — `useRef<number | null>` couldn't hold `setTimeout` return typ…
3. **Build script with `VAULT` env** — the `build` script tried to copy `dist/` to `//.obsidian/plu…
**Verification:**
- `pnpm install` → all 190 packages resolved
- `tsc -noEmit -skipLibCheck` → exits 0
- `pnpm run build:dist` → exits 0, produces valid `dist/main.js` (3MB, 74k lines) and `dist/styles.…
- Server component (`server/main.ts`) → launches with `tsx`, listens on port 3000, returns 404 on `…
No test framework is installed and none exists in the dependency tree. The one test file (`src/test…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Installed in 3 minutes.
  • Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • An agent with no time limit did not get it running.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Unverified80.000.02
Argusic Runner1/3Unverified80.000.06

Topics (from GitHub)

calendarobsidiantask-managertime-blocking

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/obsidian-time-ruler.svg)](https://argusic.com/subject/obsidian-time-ruler)

Questions

Does obsidian-time-ruler run?
Argusic could not verify that obsidian-time-ruler runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test obsidian-time-ruler?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit afbede327bc5. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test obsidian-time-ruler?
The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does obsidian-time-ruler take to install?
3 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does obsidian-time-ruler need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing obsidian-time-ruler?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for obsidian-time-ruler?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion