8000 feat(automations): an automation's runs, what's coming up, its variables and costs, in tabs by adeelahmad · Pull Request #600 · adeelahmad/lense · GitHub
[go: up one dir, main page]

Skip to content

feat(automations): an automation's runs, what's coming up, its variables and costs, in tabs - #600

Merged
adeelahmad merged 1 commit into
mainfrom
claude/project-thread-li6m25
Oct 18, 2026
Merged

adeelahmad merged 1 commit into
mainfrom
claude/project-thread-li6m25

Conversation

@adeelahmad
Copy link
Copy Markdown
Owner

Requested by Adeel · project thread

Description

Before: an automation's page in the web app was only its builder. Its runs, what it would do next, its saved variables and its costs could be read only over the API and MCP.

After: an automation's page has its switch, Run now, and five tabs. ?tab= in the address opens one.

  • Edit: the builder.
  • Runs: newest first, 20 at a time, with Older runs for the next page. Each run says how it went, what started it, what its actions did and what it cost. Opening a run shows each action's outcome and the run's log. A run held over a budget offers Run it once or Skip. Run now switches to this tab.
  • Coming up: its next schedule times, at times and actions that wait, soonest first.
  • Variables: what it keeps between runs. Enter sets a value, Clear is undone from its toast, and a new name and value are added with Enter.
  • Costs: its budget and the calls it made.

Motivation and Context

Workflow studio M11 (Studio UI), Build step 8: "an automation's page: runs, upcoming, variables, costs". It builds on the list and builder (#587).

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change; ! in the title)

Checklist:

  • The title is a Conventional Commit.
  • My code follows the code style of this project (make hooks checks it on commit).
  • I added or updated tests: automation-detail.test.tsx, 6 tests. They cover:
    • the pure helpers;
    • paging Runs and opening one;
    • Run it once on a held run;
    • Coming up, with and without times;
    • Variables: Enter, Clear and Undo, and adding one;
    • ?tab=, and Run now switching to Runs.
  • My change requires documentation updates: docs/automations.md (An automation's page), README, docs/requirements.md.
  • CHANGELOG: n/a, the title says it.

Local CI (ci/local-ci.sh HEAD --jobs frontend,pre-commit) on this head: Next.js pass, pre-commit pass.

Done questions (AGENTS.md)

  • Goal: one part of M11; merged on green.
  • Agents: runs, upcoming, variables and costs were already in the API and MCP. This adds the person's view.
  • Zero setup: nothing to install or set.
  • Fewest clicks: Enter sets a variable, and Clear is undone instead of confirmed. Run now lands on the run.
  • Configurable: n/a, no new settings.
  • Light: frontend only, no new dependency.
  • Private and secure: n/a, no new surface. It uses the same endpoints and checks.
  • Cost: the Costs tab reads the activity ledger and the budget. Nothing new calls a model.
  • User decides: a held run waits for Run it once or Skip.
  • Upgrades: n/a, no stored data changes.
  • Honest: docs and README describe exactly these tabs.
  • Tested and documented: tests added, docs updated, no generated files change.
  • Open: n/a.
  • Reported in the project thread.
  • Reuse: Tabs, BudgetPanel, ActivityPanel and the run status badges from the workflow model.

Generated by Claude Code

…les and costs, in tabs

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AjJqXgjj1cNdKGRQbX5frb
@adeelahmad adeelahmad self-assigned this Oct 18, 2026
@adeelahmad
adeelahmad merged commit 22b7728 into main Oct 18, 2026
10 checks passed
@adeelahmad
adeelahmad deleted the claude/project-thread-li6m25 branch October 18, 2026 13:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

0