Terminal & TUI Stack

goto A foundation for smart directory navigation

A small, spec driven Go command foundation for resolving an entity to a directory. The core resolver and shell integration remain planned.

Engineering story View source

Project snapshot · measured 2026-10-26

Key facts

Commits 45Last commit 2026-10-25 Source receipt ↗ Commits · 7 days 4 Source receipt ↗ Tickets closed 6 / 18 Source receipt ↗ Studies 1 Source receipt ↗

12-week commit activity

2026-10-26

Aug 3

Aug 10

Aug 17

Aug 24

Aug 31

Sep 7

Sep 14

Sep 21

Sep 28

Oct 5

Oct 12

Oct 19

View 12-week data table

Week starting	Commits
2026-08-03	0
2026-08-10	0
2026-08-17	0
2026-08-24	0
2026-08-31	0
2026-09-07	0
2026-09-14	0
2026-09-21	0
2026-09-28	16
2026-10-05	23
2026-10-12	0
2026-10-19	1

Key Features

Checks its embedded YAML tool definitions against JSON schemas to catch invalid settings.
Provides the command-line foundation, shell completion and generated manual pages.
Prints a path; a shell function must run `cd` because a command cannot change its parent shell.

Verified Engineering Milestones

Embedded specs, schemas and minimal CLI (#001, 8e79b81)
Binary-versus-shell output contract (536d618, b6271f2)
Architecture and MVP roadmap (f4d8b73, 9c10755)

Stack

Go 1.26.8, Cobra, YAML v3, JSON Schema

Why goto

Projects, bookmarks, and mounts often need different navigation tools. goto’s design brings them behind a single command, delegating specialized work to existing programs. Its first milestone establishes the command and configuration contracts before implementing the integrations.

What is implemented

Validated embedded specs

YAML specifications and JSON schemas describe command text, resolver order, and external tools. Loading rejects unknown fields and tests check cross-file relationships.

CLI foundation

The shipped scaffold includes Cobra commands, command completion, and man-page generation.

A deliberate output contract

The design reserves stdout for a directory and stderr for hints and prompts. A future shell function will perform cd because a child process cannot change its parent’s directory.

Recent milestones

2026-10-02 — Added the Go module, embedded specifications, CLI, completion, and man-page support. 8e79b81
2026-10-02 — Documented the binary-versus-shell split and output contract. 536d618
2026-10-02 — Refined terminal detection and confirmation behavior in the design. b6271f2

Historical milestones from the review through October 4, 2026.

How the work was verified

The first foundation ticket closed after make check and make install passed. Schema checks and issue-backed designs define a stable interface for later contributors. The October 4 story records 16 commits and two Go test files; it establishes groundwork rather than a completed navigation product.

Read the full October 4 story and its facts table.

Current scope and limits

Entity resolution is still a placeholder. Project discovery, XDG paths, mounts, archives, bookmarks, zoxide, ghq, udisks, sshfs, and gio integration are planned work. The intended g shell function is not presented here as a shipped feature.

Explore the source

See the source repository for build requirements and project documentation, or browse releases.

Project details

Stack

Go 1.26.8, Cobra, YAML v3, JSON Schema

Milestones

Embedded specs, schemas and minimal CLI (#001, 8e79b81) · Binary-versus-shell output contract (536d618, b6271f2) · Architecture and MVP roadmap (f4d8b73, 9c10755)

Source

https://codeberg.org/ubunatic/goto ↗

Architecture

Layer composition

Terminal: CLI, shell completion, man pages
Desktop: Linux
Inference / AI: —
Containers / VM: —
Web: —

Engineering story

goto: the story behind the project

Most people already have several ways to jump between directories: shell history, project checkouts, bookmarks, desktop mounts, and network shares. The friction is remembering which tool handles each location. goto is being shaped as one sm…

Read the engineering story

Measurement source · 2026-10-26

Verification receipts

Commits: 45 · Last commit 2026-10-25
git -C <repo> rev-list --count HEAD; git -C <repo> rev-list --count --since=<ISO-week-Monday> --until=<ISO-week-Sunday> HEAD; git -C <repo> rev-list --count --since=<measured-date-6-days>T00:00:00 --until=<measured-date>T23:59:59 HEAD; git -C <repo> log -1 --format=%cs HEAD; ls <repo>/issues | grep '^[0-9].*\.md$'; grep -l -E '^\*\*Status\*\*: *(Closed|Done|Resolved|Fixed|Complete)' <repo>/issues/*.md | wc -l; ls <repo>/docs/studies/*.md
repositories behind spec project ids in ~/projects; private-repo filter is a safety net and matches no spec project today; missing repos reported separately; seven calendar days ending on measured date in the measuring host's local timezone; commit counts include all authors and merge commits reachable from HEAD · measured 2026-10-26
Commits · 7 days: 4
git -C <repo> rev-list --count HEAD; git -C <repo> rev-list --count --since=<ISO-week-Monday> --until=<ISO-week-Sunday> HEAD; git -C <repo> rev-list --count --since=<measured-date-6-days>T00:00:00 --until=<measured-date>T23:59:59 HEAD; git -C <repo> log -1 --format=%cs HEAD; ls <repo>/issues | grep '^[0-9].*\.md$'; grep -l -E '^\*\*Status\*\*: *(Closed|Done|Resolved|Fixed|Complete)' <repo>/issues/*.md | wc -l; ls <repo>/docs/studies/*.md
repositories behind spec project ids in ~/projects; private-repo filter is a safety net and matches no spec project today; missing repos reported separately; seven calendar days ending on measured date in the measuring host's local timezone; commit counts include all authors and merge commits reachable from HEAD · measured 2026-10-26
Tickets closed: 6 / 18
git -C <repo> rev-list --count HEAD; git -C <repo> rev-list --count --since=<ISO-week-Monday> --until=<ISO-week-Sunday> HEAD; git -C <repo> rev-list --count --since=<measured-date-6-days>T00:00:00 --until=<measured-date>T23:59:59 HEAD; git -C <repo> log -1 --format=%cs HEAD; ls <repo>/issues | grep '^[0-9].*\.md$'; grep -l -E '^\*\*Status\*\*: *(Closed|Done|Resolved|Fixed|Complete)' <repo>/issues/*.md | wc -l; ls <repo>/docs/studies/*.md
repositories behind spec project ids in ~/projects; private-repo filter is a safety net and matches no spec project today; missing repos reported separately; seven calendar days ending on measured date in the measuring host's local timezone; commit counts include all authors and merge commits reachable from HEAD · measured 2026-10-26
Studies: 1
git -C <repo> rev-list --count HEAD; git -C <repo> rev-list --count --since=<ISO-week-Monday> --until=<ISO-week-Sunday> HEAD; git -C <repo> rev-list --count --since=<measured-date-6-days>T00:00:00 --until=<measured-date>T23:59:59 HEAD; git -C <repo> log -1 --format=%cs HEAD; ls <repo>/issues | grep '^[0-9].*\.md$'; grep -l -E '^\*\*Status\*\*: *(Closed|Done|Resolved|Fixed|Complete)' <repo>/issues/*.md | wc -l; ls <repo>/docs/studies/*.md
repositories behind spec project ids in ~/projects; private-repo filter is a safety net and matches no spec project today; missing repos reported separately; seven calendar days ending on measured date in the measuring host's local timezone; commit counts include all authors and merge commits reachable from HEAD · measured 2026-10-26
12-week commit activity
git rev-list --count --since=<Monday> --until=<Sunday> HEAD
12 latest complete ISO weeks; weekly values are from spec/metrics.yaml.