meegle-cli
Command-line tool for Meegle (Lark Project). Manage work items, schedules, and data from your terminal, no browser needed.
Runssource: GitHubhomepageGoMITcommit fa10b201eab4
Go, MIT licensed. The project labels itself: cli, lark, lark project and project management.
meegle-cli runs. An Argusic agent installed it in 6 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
The Meegle CLI binary builds from source, help/version/status commands execute correctly, and all 24 Go packages plus all 12 npm tests pass
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 100 of 100 (the mean of this project's run scores).
At a glance
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.
- Install time
- 6 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- make build compiled dist/meegle; ./dist/meegle --help printed all commands; ./dist/meegle version printed '1.0.23+fa10b20'; go test ./... passed all 24 packages; npm test passed 12/12 tests
- Model tokens used
- 60,452
- Exact commit tested
- fa10b201eab4
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
ok github.com/larksuite/meegle-cli/pkg/integrations/formatting 0.024s ok github.com/larksuite/meegle-cli/pkg/runtime/cliapp 0.012s ok github.com/larksuite/meegle-cli/pkg/sdk/meegle 0.249s Everything's verified. Let me compute the final timing. Let me check the elapsed time: exec /bin/sh -lc 'echo "Install + verify complete"' in /work/repo succeeded in 0ms: Install + verify complete All tasks complete. Here's the final report: tokens used 60,452 All tasks complete. Here's the final report:
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
- Reached a running state on a clean machine, with the session recorded.
- Nothing broke on the way: zero errors between clone and running.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Took 6 minutes to install, slower than the median of the 127 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 128 cli projects Argusic has installed and timed, meegle-cli was the 98th fastest to reach a running state, and 117 of 128 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 6 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
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
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/meegle-cli)Questions
- Does meegle-cli run?
- Yes. meegle-cli runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test meegle-cli?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit fa10b201eab4. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test meegle-cli?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does meegle-cli take to install?
- 6 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 meegle-cli need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing meegle-cli?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does meegle-cli compare with the alternatives?
- Of the 128 cli projects Argusic has installed and timed, meegle-cli was the 98th fastest to reach a running state, and 117 of 128 reached one at all.
- Where is the evidence for meegle-cli?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.