Juracich Lattice

Your projects, your agents and what they know, in one place.

Lattice is a workspace for building with AI coding agents. It puts your projects, Claude and Codex sessions, unattended runs, research, AI employees, browser logins, tasks and one shared memory in a single Mac app, and lets you run all of it from your phone.

Download the Mac previewSee what it is for
Lattice · juracich

Projects

juracich2
clearway1
rydiq

Workspace

Inbox
Tasks
Boards
Research
Memory
Works
Usage

claude · fix the checkout redirect

▸ Read app/account/page.tsx

▸ Memory: billing runs in mock mode locally

✓ npm run build:check passed

codex · review the diff

▸ Reviewing 3 changed files

! Waiting for your approval

Sent to your phone

coding CLIs it recognizes
5
coding CLIs it recognizes
memory every agent shares
1
memory every agent shares
open ports on your Mac
0
open ports on your Mac
guided tours built in
8
guided tours built in

Why it exists

Agents got good. Keeping track of them did not.

A normal day now means four terminals, two agent CLIs, a few accounts, and a browser full of logins, spread across a handful of projects. Each agent starts every session knowing nothing about the last one, and the thing it figured out yesterday is gone.

Lattice is the layer underneath. Every project is one place to come back to, every agent reads from the same memory, and when you step away from the desk the whole workspace comes with you in your pocket.

Use cases

What a day with Lattice looks like.

Most of the value is in how the pieces connect. Here are six real jobs, step by step, and the parts of Lattice each one uses.

Ship a fix while you are in a meeting

You know the bug, you just do not have the hour.

  1. 1Describe the bug in plain words. Claude asks what it needs and drafts the objective, success criteria and a check to run.
  2. 2Press Start. The run works in its own branch and checkout, so your working copy is untouched.
  3. 3If it needs a command you did not allow, it stops and lists it under Approvals needed. Allow and continue picks up where it left off.
  4. 4Back at your desk: a walkthrough of what it built, a per-file diff, passing checks and try-it commands to copy.
Unattended runsApprovalsVerification

Choose a library before you commit to it

Two options, an afternoon of tabs, and no time.

  1. 1Ask the question on the Research page and pick Claude, Codex or both.
  2. 2They work read-only with web search, each in its own workspace, so neither can touch your code.
  3. 3A live map shows what each one searched and read. Seen enough? Finish & gather results.
  4. 4The findings land as Markdown in your inbox, with a macOS notification and, if you asked, an email.
ResearchInboxEmail alerts

Pick a project back up after two weeks

You remember the project, not where you left it.

  1. 1Open its card on the project board: recent file changes and the agent sessions that worked on it.
  2. 2⌘K finds what you asked an agent last time, open or finished, and opens the saved output read-only.
  3. 3Copy the saved resume command for Claude or Codex. Lattice never runs it for you.
  4. 4The agent starts with the project brief from memory: how it deploys, what to avoid, what was decided.
Project boardFind terminal workMemory

Hit a usage limit and keep going

Your main Claude account runs out mid-task.

  1. 1Lattice reads the quota message in the terminal and sends one inbox notice and, optionally, one email.
  2. 2The switching router picks the signed-in account with the most usage left, or your own priority order.
  3. 3The same pane continues with the original task, recent history and terminal output.
  4. 4Your checks run after the next turn, with up to two repair attempts if they fail.
Account continuationSwitching routerUsage

Test a signed-in web app next to the code

The bug only happens when you are logged in.

  1. 1Connect your Chrome profile once. Its website sign-ins mirror into a Lattice browser profile on this Mac.
  2. 2Open that profile in a pane beside the agent's terminal, already signed in.
  3. 3The agent changes the code; you reload the pane and check it without switching windows.
  4. 4Keep the plan on a board in the side panel, next to the terminal and browser.
Browser profilesChrome syncBoards

Keep a small AI team on a schedule

Some jobs should just happen every morning.

  1. 1Describe the employee you want. Works drafts a role, instructions and tools for you to edit.
  2. 2Give it a schedule: daily times in your time zone, an interval, or continuous.
  3. 3Talk to it in its own conversation threads, on the Mac or from the phone.
  4. 4When it needs a decision, approve once or deny from the notification on your phone.
Works employeesSchedulesPhone

Everything it does

One app instead of a dozen windows.

Your projects

Every app on one board

Lattice finds the apps inside your workspaces (JavaScript, Python and Rust) and gives each one a card: recent file changes, the agent sessions working on it, and one click back into them. Pin the ones you are in this week.

Find any terminal's work

⌘K searches what you asked and what came back across every project's terminals, open or finished, and jumps to the exact pane. Saved output opens read-only and never restarts a CLI.

Resume where you left off

Resume commands printed by Claude, Codex, Gemini and Cursor are saved per project, up to 100 each, ready to copy. Lattice never runs them for you.

Agents you started elsewhere

Claude Code, Codex, Gemini, Aider and Cursor Agent sessions running in other terminals show up on the Projects page with their folder and elapsed time. Read-only, and nothing to configure.

Your agents

Claude and Codex side by side

Save a fleet of Claude and Codex terminals for a project. Each runs its own conversation over the same files, in tiled, canvas or detached windows.

Context you can see

A live context-window gauge on each pane. Enhance context builds a reviewable packet of files, notes, tasks and recent work and drafts it into the terminal, never submitting it for you.

Hand work between CLIs

Copy a handoff from one terminal and paste it into another, or hand the pane to another CLI or account after reviewing the prompt.

Works employees

Long-running agents with a role, a schedule and a conversation, in a searchable team directory. Their review requests land inline and on your phone.

Paying attention for you

An inbox that can answer

Questions, finished tasks and errors from every workspace. Yes/no prompts and numbered menus show their exact choices, so you can reply without opening the terminal. It never picks for you.

Bear watches the work

The built-in watcher. In Observe it suggests next steps; in Auto-type it can follow up in the terminal you choose, within limits you set.

New write-ups, surfaced

When an agent writes a new Markdown report into a project, Bear offers to open it, formatted and read-only, inside Lattice. Edits to old documents stay quiet.

Alerts that mean something

Terminal bells never raise alerts, because redraws and keystrokes cause them too. Only detected questions, completions, limits and errors do.

Around the code

Your logins, inside the app

Persistent browser profiles live next to your code. Optionally mirror website sign-ins from a Chrome profile, one way, on this computer. Passwords and extensions are never imported.

Tasks that can start work

List and board views with priorities, labels and due dates, synced with your Juracich workspace. A task can prepare a mission for an agent, which you review before anything runs.

Boards

Infinite-canvas whiteboards that sync with juracich.com, work offline, file under projects and share as view-only links.

A shared drive

Workspace files on the Mac, the phone and the web, up to 100 MB each, with recoverable trash. Agents can save reports straight into it.

Make it yours

Describe a theme

Type what you want, like “dark aurora with teal accents and a rounded font”, and Lattice builds a readable theme for the app, terminals and editor. Generated locally, no AI account needed.

⌘K for everything

Projects, pages, boards, terminal history, Remember… for a quick memory note, and the tours, all from one palette.

Keeps running in the background

Close the windows and the work carries on; Quit stops it. A menu-bar icon and a global quick-action shortcut stay one keystroke away.

Guided from the first launch

A four-step setup, eight guided tours, including a nine-chapter tour of the memory, and searchable help. Skip any of it and replay it later.

Terminals and search

Every terminal is searchable, and none of them get lost.

Lattice records what you asked each agent and what came back, across every project, even when the page is closed. When you need it again, it is one shortcut away.

  • All, Still open, History

    Filter across up to 1,000 recorded terminal runs, with their detected questions, turn endings and usage limits. Common credential strings are redacted before anything is saved.

  • Output history that survives

    A separate reader keeps the text across screen clears and full-screen CLIs. Shift + scroll up opens it while the agent keeps running.

  • Switch projects without losing your place

    The 16 most recent terminal displays keep their scroll position and keep receiving output while you work elsewhere.

  • Repair, don't restart

    Repair display reconnects a garbled pane to a fresh display without restarting the CLI or losing the conversation.

redirect⌘K
AllStill openHistory

  • why does the redirect loop on /billing?

    clearway · claude

    Turn ended

  • review the lattice page diff

    juracich · codex

    Question

  • redirect old ride links to the new route

    rydiq · claude

    Running

  • add a test for the billing redirect

    clearway · codex

    Usage limit
↵ jump to paneSaved output opens read-only

Bear, the watcher

A second pair of eyes on every terminal.

Bear sees what is happening across your workspace and tells you what is worth doing next. When you want it to, it can also keep a task moving on its own, always within limits you can read on the screen.

Observe

Watches terminals, waiting questions, tasks, runs, context pressure and browser panes, then suggests next steps that cite what it saw. It never types and never starts anything.

  • •AI summaries are opt-in and only run when something changes
  • •Prepare follow-up run opens a reviewed run form, never a running one
  • •Offers new write-ups to read, once each

Auto-type

Give a Claude or Codex terminal a goal and Bear follows up in that terminal until it is done or hits its limits. Several goals can run in separate terminals.

  • •Off by default; every goal needs an explicit Start
  • •Five follow-ups, ten decisions and twenty minutes per goal
  • •Typing yourself, Stop or Pause hands control straight back
Observe Monitoring all workspaces

clearway has a new write-up

docs/BILLING_REDIRECTS.md was added by the Claude session.

View documentLater

The billing tests are still unverified

The run passed its build, but no test covered /billing. Seen in 2 terminals.

Prepare follow-up run

Auto-type · claude 2

Goal: migrate the settings page to the new form components

Stop

2 / 5

Follow-ups

4 / 10

Decisions

7 / 20

Minutes

Unattended runs

Hand it a goal. Come back to a result you can check.

Unattended runs take a job from description to verified change while you do something else, in their own branch, with the permissions you chose and a check that has to pass.

  • Set it up in conversation

    Describe the job in plain words. Claude asks what it needs and drafts the objective, the success criteria and a check to run. You review the form and press Start yourself.

  • Isolated and verified

    Each run works in its own checkout and branch with the permissions you saved. It finishes as succeeded only when the verification passes, with up to two repair attempts.

  • See what was built

    A walkthrough of what it built, what it ran and what is still unverified, a per-file diff, and try-it commands to copy.

  • Approvals, not surprises

    Commands the run was not allowed to use show up as Approvals needed, with an editable rule. Allow and continue picks up where it stopped.

  • Talk to it while it works

    Send direction at any time. By default your message interrupts the current step; queued messages must be read before the run can succeed.

  • Finish now, or restart from saved work

    Finish now asks for a wrap-up from the work so far. An interrupted run restarts in the same branch with its transcript and evidence, without resetting its limits.

Fix the checkout redirect

clearway · lattice/run-checkout · 6 turns · est. $1.84

Succeeded

Keep the old /billing URL working too.

Added a redirect from /billing and a test for it. Running the checks again.

Approvals needed · allowed and continued

Bash(npx playwright test:*)

What Claude built

app/account/page.tsx+18 −6

lib/billing/redirect.ts+31 −0

  • ✓ Typecheck
  • ✓ Unit tests (42)
  • ✓ Production build

Discovery and research

Ask a question. Get a sourced answer, not a guess.

Research runs Claude, Codex or both at their highest reasoning settings, with web search and nothing else. You watch what they read as they go, and stop them whenever you have enough.

  • Claude, Codex or both

    Paired research runs both side by side in separate workspaces, each with its own report, so you can compare what they found.

  • Read-only by design

    Researchers can search the web and read, never edit or run commands. Pick a project and its committed code becomes read-only context.

  • A map built from real activity

    Every node is a search, a page read or a file inspected, with real counts and times, not a made-up progress bar.

  • Findings where you are

    One alert when every researcher has stopped, in the inbox and as a macOS notification, plus the findings by email if you ask.

Zustand or Redux Toolkit for the dashboard?

Paired research · read-only · web search

Every node is a real search or source read
  • Claude14 searches · 23 sources
  • Codex11 searches · 17 sources
Findings → RESEARCH.md, inbox and emailFinish & gather results

The memory

Tell one agent once. Every agent knows.

The memory is a folder of Markdown notes on your Mac. Decisions, gotchas, how a project deploys, what a client prefers. Lattice hands each agent a short brief when a session starts and up to three relevant notes per prompt, found by meaning as well as by keyword and kept within a budget, so context helps instead of crowding.

  • You stay in charge. Facts an agent picks up, and the tidy-ups Lattice proposes in the background, wait in an Inbox until you accept them. Auto-accept is off by default.
  • It learns what helps. Lattice tracks which notes were in play when runs passed their checks. Notes, Inbox, Graph and Health show what is stored, how it links and what actually gets used.
  • Nothing is lost. Every save keeps the previous version. Deleting moves a note to history, and merging marks the other note as superseded, so anything can be restored.
  • Works with the tools you use. Full support for Claude, Codex after a one-time hook approval, partial for Gemini, limited for Cursor.

What a note can be

memory
A fact, preference or gotcha
decision
A choice that was made, and why
reference
Where something lives
project
How a project runs; goes in its brief
entity
A person, service or account
log
What happened in a session
NotesInbox2GraphHealth

  • Billing runs in mock mode locally

    #clearwaymemoryUsed in 14 sessions

  • Moved sessions to signed cookies

    #juracichdecisionUsed in 6 sessions

  • Run the production build before calling it done

    #preferencememoryUsed in 31 sessions

Inbox · captured by codex in clearway

Stripe webhooks need the raw request body

AcceptEditDismiss

Stored as Markdown on your Mac · ~/.juracich-aso/vault

Usage and accounts

Know what you are spending. Never stall on a limit.

Lattice reads your CLIs' own logs on your Mac, so usage is there without another login. When an account hits its limit, the switching router picks who takes over: the account with the most left, or your own priority order.

  • Usage you can plan around

    Tokens and API-equivalent value from your local CLI logs, refreshed every 30 seconds, by provider, model, account and project.

  • Goals and a calendar

    Daily, weekly, biweekly or monthly targets in tokens or dollars, and a calendar of every day this year and last.

  • A calculator both ways

    Tokens to dollars or dollars to tokens, with current API prices and separate cache read and write rates. Live run costs are labelled as estimates, never as invoices.

  • Hit a limit, keep going

    When an account runs out, Lattice hands the task, recent history and terminal output to another signed-in account in the same pane, then runs your checks. Claude-to-Codex handoff is opt-in.

Switching routerMost remaining usage first
  • Claude · workLimit reached

    8% left in the busiest window

  • Claude · personalNext switch

    64% left in the busiest window

  • Codex · personalQualifies

    41% left in the busiest window

  • Claude · side projectBelow 5% minimum

    3% left in the busiest window

Works employees

Agents that keep a job, not just a session.

Works employees are long-running agents with a name, a role, tools and a schedule. Lattice gives them a team directory, a workspace for each one, and a way to reach them from your phone. Works runs as its own service on your Mac.

  • Describe it, then edit the draft

    Write what the employee should do. Works drafts the role, instructions and tools, and shows what it needs before anything is created.

  • Schedules that fit the job

    Daily times in your time zone, an interval, continuous, or off. The next run and any scheduler errors show next to the employee.

  • Conversations, not just tasks

    Continue a thread or start a new one. Replies, partial output and approval status refresh while you watch.

  • You approve what matters

    Review requests appear inline on the Mac and in the phone's Agents tab. Creating an employee never grants bypass approvals or starts work.

TeamNew employee
  • S

    Scout

    Morning research digest

    Scheduled

    Daily 8:00 AM

  • L

    Ledger

    Reconciles the usage report

    Needs approval

    Every 4 hours

  • P

    Patch

    Triage new GitHub issues

    Working

    Continuous

Ledger wants to email the weekly usage summary to finance@. Approve?

Approve onceDeny

Around the code

The browser, the whiteboard and the files, next to the terminal.

Each one opens in a project's side panel, so the thing you are checking sits beside the agent doing the work.

Browser profiles

Real, persistent browsers inside the workspace.

  • Profiles are shared by workspace panes, the side panel and the Browser page
  • Connect a Chrome profile once with its companion extension and a five-minute pairing code
  • Sign-ins mirror one way, Chrome to Lattice, and Chrome sign-outs follow
  • Passwords, passkeys, extensions and history are never copied

Boards

Whiteboards that live with the project.

  • Sticky notes, shapes, text, lines and images on an infinite canvas
  • Saved locally about a second after you stop, then synced to juracich.com, offline included
  • If both sides changed, you choose Keep mine or Use theirs; nothing merges silently
  • Share a view-only link, or Generate elements from a description

Shared drive

One set of workspace files, on every device.

  • Folders, uploads, downloads, rename and recoverable trash
  • Open from the Mac sidebar, the phone's Drive tab or the web
  • Cloud files stay available when the Mac is offline
  • Agents can save reports into a folder with a built-in tool

Away from the desk

Your Mac keeps working. You keep up from anywhere.

The Lattice phone app and your Juracich dashboard connect to the same workspace, so the agent that needs a yes can get one from wherever you are.

Remote

Every Lattice window, session and project on the Mac you pick. Attach to a running terminal, send keys, or spawn a new Claude, Codex or shell session.

Agents

Your Works team: recent activity, new conversations and follow-ups, and full proposal review with approve once or deny.

Drive

The shared drive: browse, upload from the phone, and save or share files with the system sheet.

Activity

Your Mac's daily activity and its Claude and Codex usage, tokens and estimated cost, refreshed every 30 seconds.

Latticenow

Approval needed

claude · clearway needs your approval.

MacBook Pro · Online

Sessions

  • claude · clearway

    Waiting on you

  • codex · juracich

    Running

  • shell · rydiq

    Idle

Notify me about

Approval needed
Agent task completed
Agent task failed
Session ended
RemoteAgentsDriveActivitySettings

The Mac does the work

The phone is the remote. Commands that cannot reach the Mac within 30 seconds expire instead of running much later.

Previews stay private

Message previews are off unless you turn them on, and you choose which computers can notify you.

Nothing comes in uninvited

Lattice connects outbound to your Juracich workspace. No open ports on your machine, and only your own signed-in devices can reach it.

What runs where

Most of Lattice never leaves your Mac.

Here is what each part needs, and where its data lives.

  • Projects, editor and terminalsYour MacA local folder. No Juracich account.
  • MemoryYour MacA folder of Markdown notes you can open in any editor.
  • Usage and historyYour MacYour CLIs' own logs. No extra login.
  • Coding agentsYour accountsThe CLI installed and signed in, with its own plan or billing.
  • Browser profilesYour MacInternet for the sites. Chrome sync stays on this computer.
  • Tasks, boards and driveYour workspaceA Juracich account. Boards keep working offline.
  • Phone and dashboardYour workspaceThe Mac running, awake and online.
  • Works employeesYour MacThe Works service running separately; it is not bundled.

Questions

The things people ask first.

Does Lattice include AI usage?

No. Lattice works with the coding CLIs and accounts you already have. Installing a CLI through setup does not sign you in or include credits, and you can finish setup without an agent at all.

Will it run things without asking?

Runs and research start only when you press Start. Resume and try-it commands are copied, never run. Context is drafted into a terminal, never submitted. Auto-type is off until you turn it on, and each goal has hard limits.

Where does my data live?

Projects, memory, terminal history and usage stay on your Mac. Tasks, boards, the shared drive and the phone connection go through your own Juracich workspace. Saved terminal output has common credential strings redacted.

Which agents does it work with?

Claude Code and Codex get the deepest support, including fleets, handoff, usage and continuation. The memory fully supports Claude, Codex after a one-time hook approval, Gemini partly and Cursor in a limited way. Aider and Cursor Agent sessions are detected when started elsewhere.

Do I need the phone app?

No. Everything on the phone is also on the Mac, and the Juracich dashboard can reach your computer too. The phone app is not in the App Store or Google Play yet.

What happens when my Mac sleeps?

With remote access connected, Lattice keeps working while the display sleeps. Closing the lid, putting the Mac to sleep, losing the network or quitting Lattice makes it unreachable until it is back. Phone commands that cannot reach it expire instead of running later.

Get Lattice

Try the Mac preview.

Pick Apple Silicon for an M-series chip or Intel for an Intel processor. You can check under Apple menu → About This Mac.

Mac (Apple Silicon)Mac (Intel)

Preview build, not yet Apple notarized. If macOS blocks it the first time, open System Settings → Privacy & Security → Open Anyway. The signed release will need macOS 14 or later. Windows, Linux and the phone app stores are not available yet.

Already installed? Manage connected computers →
  1. 1

    Install it on your Mac

    Download the preview for your chip, unzip it, and move Lattice to Applications.

  2. 2

    Connect your account

    Sign in to Juracich from Lattice's Mobile or Settings page. That links this computer to your workspace.

  3. 3

    Leave it running

    Remote access keeps working while Lattice is hidden or minimized. The display can sleep; the computer stays reachable.