Agents
Agents that operate vs. tools you operate
Coding agents generate files. Career agents have to understand a live system: what changed, what you decided, and what is happening now. A prompt window is not enough.
A coding agent is good at generating code. Operating a career is a different job.
It requires continuous understanding of a live system: what changed, what depends on what, what failed before, and what is happening right now. That understanding cannot come from a single prompt or a fresh context window.
This is the same argument production-engineering companies make about observability. Dashboards were built for humans to read. Agents need a world model — persistent operational context — or they are just chat with extra steps.
Careers have the same gap.
Tools wait. Agents run.
A tool is something you pick up:
- paste a job description
- ask for a rewrite
- copy the output into another tab
An agent is something that already has the state:
- who you are (semantic memory)
- what you did (episodic memory)
- how you sound (procedural memory)
- what the market is doing (temporal signal)
Then it acts — drafts, flags, prepares — and waits for approval on the moves that cannot be undone.
If you have to re-explain yourself every session, you do not have an agent. You have a toy with a good model.
Why “just use ChatGPT” hits a wall
Language models are strong at generation and weak at continuity. They do not know that you declined a staff role last spring because of commute, or that your best proof of scope is a migration nobody put on LinkedIn. They do not know that “senior” in your market now implies a skill you have not practiced in two years.
Those facts are the job. Generation without them is fluent generic.
Job descriptions for AI engineers in 2026 already treat evals and agents as first-class skills — because production systems need memory, tools, and judgment loops, not one-shot completions. Career software that ignores that lesson will keep shipping autocomplete for resumes.
Human-in-the-loop is not a cop-out
Autonomy without approval is how you get a system that applies to jobs you would never take.
Terraces is explicit: the agent drafts and recommends. You approve and guide. Irreversible tools require a yes. That is not a lack of ambition. It is how you put an operator on a life without handing it the keys.
The future of AI-native careers is not a demon that job-hunts while you sleep. It is infrastructure that never forgets, never waits for panic, and never ships a move you did not authorize.
Operate the career. Don’t operate the chatbot.
