$5k in creditsends in13:00:00

Long Horizon Agents Hackathon

Portable working state, not memory.

Give agents something better than a longer conversation: a shared, editable account of the work that the next agent can pick up.

100% open source

Deployment office hours

Claim your credits See the 10-minute test
Interactive sample · fictional workspace

01 / Start where agents already work

Markdown with the power of SQL.

Keep the plain-text habit that makes agents useful. Give the decisions, tasks, people and evidence inside those notes a place in one connected, queryable working state.

See what that state becomes
WINTER ROLLOUT / RAW EXCERPTOpen in demo ↗
---
title: Publish winter timetable v3
type: WorkItem
kind: task
lifecycle: in_progress
account: Stonewick Island Market
assignee: Mara
priority: P0
related:
  - "[[Mara Ellison]]"
---

# Publish winter timetable v3

Owner: Mara. Tomas prepares the operations sheet; June checks the market and school wording. The August headcounts justify **retaining** Reedbed Saturday service. They do not authorise an extra sailing.
THE SAME WORKSPACE / SQLquery_sql via MCP

What work is still active in the winter rollout?

SELECT name, lifecycle
FROM records
WHERE type = 'WorkItem'
  AND home_id = (
    SELECT id FROM records WHERE name = 'Winter rollout'
  )
  AND lifecycle IN ('open', 'in_progress', 'blocked');
Three matching rows from the winter rollout
NAMELIFECYCLE
Add Sat 10:40 Reedbed sailingopen
Publish winter timetable v3in progress
Bearing check — Pettifordblocked

02 / One state, many forms

Live, shared truth for knowledge graphs, Kanban boards, documents and CRMs.

The work stays put. Ask for the view you need: a board to move tasks, a document to explain a decision, a graph to follow the connections, or a CRM to see the people involved.

Explore the same records in the demo
TasksGraph ↗Folders ↗Customers ↗
ALDERMERE FERRY CO. / WINTER TIMETABLEOne state. Four ways in.
Backlog1
P0 · Stonewick Island MarketAdd Sat 10:40 Reedbed sailingProposed extra; waiting for Pettiford clearance and a crew check.
in progress1
P0 · Stonewick Island MarketPublish winter timetable v3Mara's publish gate: reconcile counts, vessel clearance and customer copy.
blocked1
P0 · Fellside Primary SchoolBearing check — PettifordSam's physical inspection is the gate on any extra Reedbed sailing.

The board, the linked decision, the handoff note and the market account all read the same records.

03 / Time is part of the state

Know what’s true now. See how it got there.

Let agents change course without losing the thread. A correction becomes the current state, the earlier decision stays visible, and a fresh agent can continue from what governs now.

Decision trailOpen record ↗
D1 / SUPERSEDED

D1: Cut Reedbed, add Fellside extras

Superseded proposal based on an untested demand assumption.
NEW EVIDENCE92 Reedbed boardings · 31 Fellside boardingsHeadcounts Aug–Sep by sailing ↗ overturned the booking-sheet assumption.
D2 / CURRENT

D2: Keep Reedbed; hold 10:40 until cleared

Because the August headcounts reversed the Reedbed assumption. Retain existing Reedbed service; condition the proposed extra on vessel and crew clearance.
NEXT SHIFT / HANDOFF

Handoff — winter rollout, 22 Sep

Tomas's handoff: retain Reedbed; the extra sailing is still conditional.

Try the continuity experiment

The 10-minute test

Change something important, then see whether a new session picks up the new plan.

  1. Record one decision in Native (one prompt, one record).
  2. Change it — supersede the record, don't append a correction to the chat.
  3. Start a fresh session, switch model, or hand to another agent.
  4. Recover the current state from the record — not from history.
  5. Inspect the current decision and its change history.

04 / Make it yours

Easy to start. Yours to own.

Start with a hosted workspace and your existing agent. Keep the freedom to inspect the source, take your data with you, and shape the interfaces around your work.

THE FAST PATH

Get working in the cloud.

  1. Connect a supported client — Claude Code, Claude Desktop, Codex, or ChatGPT Desktop — to hosted Native.
  2. Claim with code HORIZON-1000 in your workspace (or tell us your workspace name in the room and we'll apply it).
  3. Build. Credits cover the event and one week after, so your project survives demo day.
Get the Native plugin MCP quickstart

For Long Horizon Agents Hackathon builders. Credits apply to hosted Native. One claim per builder. No card required.

THE OPEN PATH

Take the keys with you.

Read the code. Run your own instance. Decide what your state contains and how people and agents see it.

Explore the source

One working world, with room to make it your own.

Built for the Long Horizon Agents Hackathon. Short URL for the room: withnative.ai/horizonagentshack.