Skip to content

chore: Configure Renovate - #1

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/configure
Open

chore: Configure Renovate#1
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/configure

Conversation

@renovate

@renovate renovate Bot commented Jul 18, 2026

Copy link
Copy Markdown

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

📚 See our Reading List for relevant documentation you may be interested in reading.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.


Detected Package Files

  • Dockerfile (dockerfile)
  • go.mod (gomod)
  • tools/ttydrive/go.mod (gomod)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Hopefully safe environment variables to allow users to configure.
  • Show all Merge Confidence badges for pull requests.
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Show only the Age and Confidence Merge Confidence badges for pull requests.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitLab.com contains a link to the commit-to-commit diff
  • Correctly link to the source code for golang.org/x packages
  • Link to pkg.go.dev/... for golang.org/x packages' title
  • Provide a link to octochangelog's improved breakdown for Renovate's changelogs

What to Expect

With your current configuration, Renovate will create 7 Pull Requests:

fix(deps): update module github.com/iodesystems/agentkit to v0.4.0
fix(deps): update module golang.org/x/term to v0.45.0
  • Schedule: ["at any time"]
  • Branch name: renovate/golang.org-x-term-0.x
  • Merge into: main
  • Upgrade golang.org/x/term to v0.45.0
chore(deps): update ubuntu docker tag to v26
  • Schedule: ["at any time"]
  • Branch name: renovate/ubuntu-26.x
  • Merge into: main
  • Upgrade ubuntu to 26.04
fix(deps): update module github.com/charmbracelet/bubbles to v2
fix(deps): update module github.com/charmbracelet/bubbletea to v2
fix(deps): update module github.com/charmbracelet/glamour to v2
fix(deps): update module github.com/charmbracelet/lipgloss to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-charmbracelet-lipgloss-2.x
  • Merge into: main
  • Upgrade github.com/charmbracelet/lipgloss to 733ce53541bb688fd735524b665e0d96e35433bb

🚸 PR creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prHourlyLimit for details.


❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.


This PR was generated by Mend Renovate. View the repository job log.

Nthalk added a commit that referenced this pull request Aug 2, 2026
The agents pane made a resident child visible; it did not make it REACHABLE. It
had no selection, background jobs had no presence at all, and a child's
conversation was unreachable by construction. The human could see that a child
was spending tokens and could not see what it was doing.

The rule that organizes it, and the reason it is worth building this way: `▸`
means descendable. Focused, → opens and descends and ← ascends — the same
gesture on the collapsed strip, on a row, on a job's output, and on the docs
blocks that already worked this way. One affordance, learned once.

  dun dev ~/src/dun · 12 tools · 2 agents
  › formalize the jobs table and keyboard nav…        ← the last thing you asked
  ▸ ▸#1 running 2m 6.5kt · ✓#2 idle · ⚙job 3 1m0s  ⟩ go test -race ./...

Two header lines in steady state, and NEITHER when there is nothing to say, so
a session that never delegates loses no space. Collapsed costs one line no
matter how many children exist; → expands it to a table capped at 6 rows that
scrolls, because children are uncapped and jobs accumulate for the life of the
session.

Focus is three zones cycled by tab, in screen order from the bottom up. An
empty activity zone is SKIPPED rather than focused-but-blank, which is what
preserves the two-way tab everyone already has in their fingers.

Selection is stored by IDENTITY, not index: rows are rebuilt on every event and
a new agent shifts every job down, so an index would silently walk to a
different row while you were reading it. Row order is stable for the same
reason — sorting by interest would move rows under a selection.

Descending into an agent is a SCOPE SWITCH, not an overlay: the task line
becomes the child's prompt, the conversation becomes the child's, and the strip
becomes a `↰ parent` row that takes you back. The input stays live and routes to
that child through the same engine path as agent_monitor(tell:), so there is one
definition of what telling a child means. A new human→child channel that
children were denied on purpose (they have no ask_user) — accepted, because the
human is not the model and the point of the pane is that a child is steerable
rather than merely observable.

The child's scrollback is PULLED (a new `agent` command → `agent_history`
event), not pushed. Its callbacks are nil by design, and un-nil'ing them would
mean tagging and forwarding N streams nobody is looking at. Pull also works
unchanged for a STOPPED child, whose process is gone but whose transcript is
not — which push could not do at all. A reply for an agent we have already left
is dropped, or a late response would paste someone else's conversation over
this one.

Clipping is width-aware and applied to PLAIN text before styling: clipping a
string that already carries escape codes counts them as characters and can
leave a colour turned on for the rest of the line.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.

0 participants